Pricing, telemetry, Mac first?
Nope.
We Built Syntax Highlighting for the Terminal Input Editor
11–20 of 23 posts
Re: We Built Syntax Highlighting for the Terminal Input Editor
#12Pricing? Telemetry? Mac first?
Nope
Re: We Built Syntax Highlighting for the Terminal Input Editor
#13"pricing" "telemetry" Moving on.
There is not a universe that exists where I would give an unsigned, non-reproducibly-built, proprietary third party binary control of the terminal I use to access code and systems of my clients, or send a third party any data about them. It would be negligent on my part.
Also most of the capable sysadmins and CLI junkies that I know use Linux. Not supporting that first is a strange choice.
As cool as this idea is, I feel the only way I could ever responsibly have it is by ripping it off and actually making it open and available to all platforms.
Re: We Built Syntax Highlighting for the Terminal Input Editor
#14"pricing" "telemetry" Moving on.
Telemetry is definitely a no-go for a tool like this, but professional engineers (usually very highly paid) really need to get over their free tool addiction. Good tools in every profession cost money. We'd probably get even better tools if creators knew they could earn some money for delivering value.
Would be interesting to read what are highly regarded tools in different occupations. For example, I read that a particular type of whiteboard chalk was highly regarded by mathematicians.
Re: We Built Syntax Highlighting for the Terminal Input Editor
#15I loved this until I read the comments on the original Warp submission. Sorry, I'm not logging into my terminal.
Re: We Built Syntax Highlighting for the Terminal Input Editor
#16I loved this until I read the comments on the original Warp submission. Sorry, I'm not logging into my terminal.
I just downloaded it, saw a login wall and noped out.
Re: We Built Syntax Highlighting for the Terminal Input Editor
#17"pricing" "telemetry" Moving on.
Jess from Warp here! Just wanted to clarify that Warp is completely free for single users :) And in terms of telemetry, Warp never sends the contents of terminal commands and outputs to our servers (unless a user explicitly chooses to use the "Block Sharing" feature). What Warp currently sends in regard to telemetry is listed here: https://docs.warp.dev/getting-started/privacy#exhaustive-tel... Hope that helps!
It is not personal, but I do not trust you.
Re: We Built Syntax Highlighting for the Terminal Input Editor
#18I loved this until I read the comments on the original Warp submission. Sorry, I'm not logging into my terminal.
I really like this idea too. Hopefully someone comes along and makes an open source terminal that does the same thing but without the shady stuff.
Re: We Built Syntax Highlighting for the Terminal Input Editor
#19Earlier quoted context omitted.
Jess from Warp here! Just wanted to clarify that Warp is completely free for single users :) And in terms of telemetry, Warp never sends the contents of terminal commands and outputs to our servers (unless a user explicitly chooses to use the "Block Sharing" feature). What Warp currently sends in regard to telemetry is listed here: https://docs.warp.dev/getting-started/privacy#exhaustive-tel... Hope that helps!
It is not personal, but I do not trust you.
Someone on HN said something along the lines of "Trust is a last resort" and I find myself repeating it a lot.
Re: We Built Syntax Highlighting for the Terminal Input Editor
#20Earlier quoted context omitted.
Hey there! Advait here - author of the blog above. That's awesome to hear, hopefully you enjoy trying out Warp and switch over to it full-time ;)! That's an interesting point you raise - definitely agree that there's tons of wasted efforts solving the same problems multiple times. With Warp, the eventual hope is to build an ecosystem for developers to be able to collaborate with each other and build reusable extensio…
How to create an ecosystem, I'm not sure (although discussions like this on HN would go a long way). But how to identify common patterns of problems? I think we just need to make an effort to zoom out and consider the phases of software development and infrastructure management we do, then look for similarities. For example on the web development side, we routinely build web application foundations which require auth…
Yep, ahaha - creating an ecosystem is a massive undertaking but an interesting topic to dive into.
Agreed - I like the aspect of trying to distance ourselves from the existing paradigms and modularizing the world. It'd be insanely awesome to have a common space to share these creations - I guess GitHub is one of the ways to do this but stuff definitely isn't as cohesive as you'd want it to be, in that each solution isn't meant to easily work with others. App-specific extension stores get closer to this vision but are limited to a specific application.
This gets me thinking about whether it'd make sense for software to have more standardization, in the same vein as ISO standards but with a focus around interoperability between such modules? However, standardization also brings a lot of drawbacks, as we've seen with ISO or ECMA's committees where bureaucracy blocks innovation, hence I'd be both excited and wary about authoritative universal software standards.
It's interesting to see that in the hardware space, we see the issue of interoperability being tackled more broadly due to the limitations of "needing" to be compatible with other pieces of hardware, for many use cases. Though, you always have proprietary standards within this space as well.