HN user
https://imagine27.com https://twitter.com/jng27
Plenty of rationalization of how java (the language) is "subjective for developers" in terms of productivity and happiness. From a non-engineer view though, let's be real : nobody ever got fired for picking java. This was just a decision made in favor of managers over the poor engineers that will have to deal with maintaining a large Java code base over time.
If you have used Rust in any real world capacity on actual projects you know that there are no "Little Books" when its comes to using Rust. An overly complex and unproductive language as much as C++.
Most applications I tend to see don’t even use concurrency because they are so small and simple that they don’t need it.
Have you debugged.it ?
While I had over a decade of experience in other languages, such as Python, PHP, Java, etc.
I found it extremely difficult to wrap my head around Go.
Maybe it's not Go that is a terrible language but just that the author is not a systems programmer who has worked with large code bases ?
Maybe, however the author has over 20 years of professional Lisp experience, there are interesting points made for anyone in that category. To be fair though, did you read the post ? The intended audience is much wider than you're assuming.
The irony of this is next level, after all Microsoft has been threatening innovation for decades.
This sounds more like their typical corporate propaganda to get workers back onto their campuses and under the whip of their middle-management class.
After using Rust for a few years professionally it's my take that people that really want to use it haven't had much experience with it on real world projects. It just doesn't live up to the hype that surrounds it.
The memory and CPU savings are negligible between Go and Rust in practice no matter what people might claim in theory. However, the side effects of making your team less productive by using Rust is a much higher price to pay than just running you Go service on more powerful hardware.
There are many other non-obvious problems with going to Rust that I won't get into here but they can be quite costly and invisible at first and impossible to fix later.
Simple is better. Stay with Go.
I wrote Pong in Clojure back in 2009 in <200 lines. https://imagine27.com/pong_in_clojure
They are still classes, still live on the heap and still need to be garbage collected. Compare with value types that live on the stack in other languages such as Swift, Go and Julia.
Flimsy counter-argument.
It's just not true. Ryzen laptops have been available for months for a fraction of the price of a macbook that are just as impressive. https://imagine27.com/rise-of-the-mac-serial-killers
I've used Mac hardware for over 25 years and own both laptops.
It runs Linux perfectly.
Article author here and owner. It's just not true. The screen, thermals and noise are nothing like the review.
Bezos has plenty of his own narrative fallacies going. https://www.youtube.com/watch?v=RVVfJVj5z8s
Code is here --> https://github.com/justinmimbs/rs-asteroids
Misleading title. Alpha releases aren't considered general releases.
A Ruby subset in Common Lisp (circa 2010) https://imagine27.com/ruby_subset_implementation
Lost all credibility at "... Age and experience will be less valued ...".
Another case in point. http://www.latimes.com/local/lanow/la-me-ln-tesla-collision-...
The article seems to paint Kotlin as not really much of a functional language as Scala is but more of a Java replacement. This is just not true. Both languages will not stop you from writing imperative code just as much as either can be used for a very functional style of programming. It really comes down to the caliber of developer and not the language choice here.
Out of the frying pan and into the fire.
Software Engineering in 2017 : Personality cults and mostly a lack of appreciation for the history of CS.
Go is a lowest common denominator language designed by a large company to make programmers expendable. It's ironic though because we all know how that worked out after Sun tried it with Java and what we now have some 20+ years later.
I think after a decade of "Cloud" hype that many customers are finally realizing that the costs/benefits of using a provider are just more complicated and more expensive for most of their needs.
This is a startup that provides "valuations" of other startups after all. They sell shovels to the miners who think they are all going to get rich.
What would you guess the average years of experience are for a Y Combinator founder ? I say this not as a judgement but simply because people earlier on in their careers often need more face to face guidance to help them get to the point where they have more experience.
It's a fact that having everyone in an office 5 days a week sadly and far too often does not result in a company getting what it wants built. The problem with that lies elsewhere, usually with management and hiring.
This actually sounds workable. One other thing that is clear is that a 5-day onsite 40 hour work-week is not productive. IMO a 4-day week split between office and home would be way more productive.