Comment by savmat
4 years ago
I’m sick of programming languages that use “fast typing” and “productiveness” as a selling point. There’s no selling point in being productive doing a counter in a few seconds, production scenarios are far more complex and very often all those new programming languages fall short to their promise. Btw I don’t want to be fast or productive, I want to write code that works decently and is great for other humans myself included
It depends. If your work is to create a new counter app every day to support some specific, single usecase, in other words you write a lot of simple apps and not a single complex one, then it’s definitely a win for productivity.
> create a new counter app every day to support some specific, single usecase
sounds like the kind of thing that programming was invented to eliminate
Who actually does this for a living? And where do I sign up? :D
In all seriousness, I've never worked at a company that did anything like this. What is the use case for creating lots of small apps as opposed to maintaining a larger product?
Another marketing pet peeve that I have is term "blazing" fast. I think it's so overused now on any new tool's landing page posted online that I instantly just assume that it is, in fact, of relatively average speed. Are there no other synonyms for fast these days?
That's not really a complaint about languages so much as it a complaint about marketing though, is it?
I don't go learning every language to mastery level, but I try to at least keep track of whereabouts they lie in the spectrum so I can cut through marketing-speak when I see it.
The way I see it, if a thing is being dogfooded in production, it's production grade. People can debate go-vs-rust or whatever till they're blue but the reality is simply that you can ship something with either and there are always going to be proponents and detractors for each side.
While I haven't followed Imba that closely, I've been aware of it for years, and I have to say it's one of few projects that actually has interesting technical takes on several fronts.
Then don't use it. Some of us do like productive (ie. expressive and batteries included) languages. PHP, Python, JavaScript and Ruby still power most websites. There's plenty of choices for enterprise languages and frameworks if you want.
Productive, everything included languages/frameworks such as this are great for freelancers, designers, students, and anyone who wants to get up and running quickly. You can also still create maintainable projects with expressive languages (Google and Python, GitHub and Ruby are a couple examples).
People are doing things that don't break with 'productive' languages.
Considering Javascript is the only language supported on the frontend, claiming to be more productive is definitely valid.
Coffeescript was a breath of fresh air compared to writing ES5.
I sure am tired of Javascript being the lingua franca of the web. Imagine if we decided C was good enough and now all programming languages from that point on should just be something that cross-compiles to it.
Isn't that what WebAssembly is for? It's kind of the web version of C pretending that everything is a PDP-11.
Support WASM then?
We need a Coffeescript Renaissance!
World needs a version of coffeescript that compiles to typescript.
1 reply →
Nothing is holding you back from using it!
7 replies →
Fair enough - and so you skip the languages that doesn't fit that bill for you and pick one that you feel bring you those outcomes. No hurt feelings!
I don't see the value in being able to "type fast".
I see it in less visual clutter.
Yes. Which gives you more control over how you make the code look. DSLs.
You could be doing stuff that works decently, is great for humans, and still be productive (maybe even fast). Or figure out how to do it faster next time.
Someone else may want you to be fast and productive. Or... they'll find someone else who can provide what they want who is faster and more productive than you.