497 karma · joined July 24, 2022
Most recently, during COVID, I was laid off with no contact with my manager and no explanation. My recruiter called right before my access was terminated at 5pm.
Secondly, we now see a company whose products have severe safety defects due to the influence of cost-cutting managers, more concerned with profits than quality.
Because governments can't fund projects?
Not sure what you are arguing for, but IMO there is this idea of the "great men" who build cool things like Space-X. So we should let the wealthy keep their great wealth so that we get more companies like Space-X.
Except what we really get is more corporate looting, oppression and monopoly, plus the hyper-wealthy having excessive influence over government.
If the wealth is spread around, and we no longer have to be wage slaves our whole lives, then collectives of like-minded people could band together and build cool things. We do see that in the open-source world, but most contributors are not earning money they need to pay bills.
Progressive taxation is a good idea...
As I understand it, Rust lacks do-notation and higher-kinded types, making it hard to have true monads in Rust.
Scala would be the language with monad support comparable to Haskell.
I can only guess what these "Scala experts" were doing, there are certain language features that can slow your compile times, and libraries like Shapeless that leverage those features in amazing ways, but can kill your compile times.
Scala is a toolkit that enables amazing things, but you have to understand the trade-offs, both in terms of compile time, and understandability of the code.
>In the real world, types have traits/interfaces/expected attributes etc. and type erasure prevents the compiler to verify this when using binary dependencies, which is obviously _not_ what one wants in a statically compiled language.
Scala has ways of recovering the information, such as using context-bounds and type manifests. Scala can actually verify an amazing amount of constraints at compile time, but the more exotic tricks will increase compile time.
What you are complaining about are foot-guns that rarely happen in my 20 years experience with JVM languages (I think generics were added in Java 5, but still...)
It could be x1.2 slower, maybe even 2x, and I wouldn't notice it, because it is fast enough. IntelliJ has incremental compilation. Compile times only matter when I do a full rebuild, and it is still fast enough.
If I had to build a giant mono-repo like at Google, then the compile speed of languages like Go become important.
For a typical micro service, I never think about compile time, thanks to incremental compilation. Even a full compile is not bad. Tooling is also fine, although Scala 3 set things back. IntelliJ now supports Scala 3 adequately.
def foo[T](t: T): T
If the function is truly generic, then we know nothing about the implementation details of T. The only meaningful implementation of foo is identity: def foo[T](t: T): T = t
From a FP perspective, T should be erased, and the programmer should not cheat and use reflection. The type signature should tell you much about what the function does.I've used Scala professionally for the last 8 years. The tooling is fine, assuming you avoid exotic libraries like Shapeless. Compile times are fast enough that I don't think about it much, using IntelliJ incremental compilation. A full recompile of a micro service might take 30 seconds, whatever it is is not a big deal IMO.
> opening projects in an IDE like IDEA could take up to 30 min on high end workstations
This is insanely wrong. Maybe you are operating on experiences from 10 years ago? I have a new M2 MacBook Pro, and opening projects is quite fast. The first time you do it, it will resolve the SBT dependencies and index files. That can be done in the background, and is probably less than a minute for a typical project. Even my previous laptop could open projects quickly despite being 3 years old.
> the Scala data structures have been at least an order of magnitude slower than the JVM native ones
They are slower, but not an order of magnitude slower. Perhaps you are remembering the infamous email from the Yammer CTO that got leaked, but that was a long time ago, and the compiler and libraries have improved greatly since then.
But yes, in performance critical code, you can just switch to an imperative style and use Java collections.
I don't have time to explain the benefits of Scala features, but I'll just point out that other than implicits, many ML inspired features of Scala have made their way into modern languages, including Java, C#, Rust and Swift. Scala didn't invent those ideas, but repackaged them in a novel way.
The reason I work for a soul-less telco, is that it is hard (for me at least) to find a job in the first place. I've been at plenty of small companies as well. If I could have gotten in at Google I would have done it in a heart beat, not just for the money, but to have FAANG on my resume.
My career went in to the toilet in my 40s, and it has never really recovered. However, I'm an introvert and on the spectrum, so I lack good networking skills and never moved up the career ladder.
Even so, among my circle of friends there is a consensus that many of us were struggling around age 50, and now I am 60. The only jobs I've had in the last 5 years have been contracts. My current gig, I haven't seen a raise in 3 years, despite 20% inflation. I've been told that the company I work for has a freeze on raises, so I will have to start job hunting...
One friend in a group chat has an android, and that hoses the messages I send out, because Apple will default to SMS. It is quite maddening.
The main complaints from other seem to be about high def videos, pictures etc, which I don't personally care about.
I've been wondering for a long time why we don't have whole-house heat recovery systems.
I have a Prius Prime, and the charge is enough for driving around town. If it had a 50% larger battery, it could have gotten us to work on one charge. But we don't commute since the pandemic.