still_grokking

5 ms·

31.
by still_grokking 7mo ago
Just use µBlock Origin for most of the annoyances, and for the stupid google popup a simple Stylus CSS rule is enough.
32.
by still_grokking 7mo ago
TBH, you could change a few terms and that text wouldn't look much different in the 90's. Microslop never gave a shit on end-users and what they think. Nobody ever "liked" Microslop. People were always complaining that W
33.
by still_grokking 7mo ago
Most client PC are still running on Microslop Windows. They are, as always, using Windows to sell all their other crap, especially Azure and 365. Things like their AD or office tools are tightly integrated into the cloud so you realisticall
34.
by still_grokking 7mo ago
> mail, maps, docs, search, etc. It would be pandemonium I would hardly notice, TBH. There are alternatives for all of that.
35.
by still_grokking 7mo ago
I'm not sure where you are but at least here Microslop is still ruling more or less everywhere besides the online ad market. They are big in everything that is mass scale developer oriented with things like GitHub, VSCode, or all their
36.
by still_grokking 10mo ago
> But safety is not the only important aspect of a programming language. That's also part of what I've said. The point still being: Where you need a safe language there is no way around it, and Scala is still one of the very fe
37.
by still_grokking 10mo ago
> Python has convenient and good type design with str.join ignored by other languages. Of course such non-discoverable and unintuitive design gets ignored everywhere! We just established that even in Python the correct way to do it would
38.
by still_grokking 10mo ago
That's obviously the wrong signature. The semantically correct one is "Container[T : Printable].join(): String"; T must implement the Printable concept, but Python lacks concepts (or type-classes as these are alternatively ca
39.
by still_grokking 10mo ago
> or Scala 2, yes, or there was the last I looked. Still the best Scala development experience by some margin, sadly. I can't find it. Could you link to that "best Scala development experience by some margin"? All I know i
40.
by still_grokking 10mo ago
I still don't get what you want to say. Linking some GitHub repo does not explain anything. What is "abuse", what is "magic" in this context?
41.
by still_grokking 10mo ago
First of all nothing in the article is about optimization. Scala does not even have an optimizer… It was about translation strategies and macro expansion. But this makes no difference. You have all issues you just named exactly the same in
42.
by still_grokking 10mo ago
The website is a private undertaking which started literally a few days ago. It's not some official complete tracker. The point was to show that big corps are dependent on Scala, often at their core. Scala is likely not for everybody,
43.
by still_grokking 10mo ago
Examples and code snippets in the official docs of course default to the new syntax, making them well readable for all people accustomed to Scala's new syntax. > If I recall correctly, later they added a switch allowing one to choos
44.
by still_grokking 10mo ago
Scala 2's macros are compile time constructs. There is no runtime code generation / staging. Scala 3's macros support staged compilation, so you can have macros which create code in later stages at runtime. https:/&#x2F
45.
by still_grokking 10mo ago
It won't in general. Doing so is a feature of high-end VM runtimes like the state of the art JVMs or JS runtimes.
46.
by still_grokking 10mo ago
> However I agree that the syntax is a textbook case of trying to fix what ain't broke. The great new syntax is the very reason I don't want to even touch Scala 2 any more. The syntax change is the absolute highlight in Scala 3
47.
by still_grokking 10mo ago
> The original language spec is the best thing the Scala devs ever made. The overreaching majority thinks that Scala 3 is objectively much better than Scala 2 ever was. That's at least what you hear just everywhere, besides the occa
48.
by still_grokking 10mo ago
Sure. All successful languages go into decades still stand. Just see how great this worked out for Java (or Perl… ;-))! /s
49.
by still_grokking 10mo ago
What's so bad about it? Why not try to learn it for good?
50.
by still_grokking 10mo ago
The upgrade Scala 2 -> 3 is usually super smooth. The compiler does all the work, you just need to update your build config / dependencies. The only exception is macros: If you used the experimental Scala 2 macros you need to migrat
51.
by still_grokking 10mo ago
> Lower-level languages don’t have this same problem to the same extent. Of course they have. If the computer would directly execute what you write down in what you call "low level language" this would be slow as fuck. Without
52.
by still_grokking 10mo ago
> Especially when the libraries abuse magic language features (and far too many Scala libraries do) Would you mind to explain what you mean?
53.
by still_grokking 10mo ago
Just for context, a lot of people in the community think that this syntax change was the best thing that happened to Scala since its inception. Also the silent majority thinks that the people who still lament over that change are just a ver
54.
by still_grokking 10mo ago
What are you missing currently?
55.
by still_grokking 10mo ago
There's still a working Eclipse plugin? Does Eclipse now support LSP servers? The most reliable Scala IDE is currently Metals (in VSCode, but other editors work, too). Metals uses directly the compiler for all code intelligence so it&#
56.
by still_grokking 10mo ago
People on HN down-voting facts? And yes, "you get what you pay for" is part of this.
57.
by still_grokking 10mo ago
https://nindalf.com/posts/stop-citing-tiobe/ https://medium.com/@ankushroy7/tiobe-is-trash-why-it-gets-mo... Tiobe bullshit unfolding looks like: https://news.ycombinator.com/
58.
by still_grokking 10mo ago
It's such a blessing to be able to write in Scala customers.map(_.name).mkString(", ") instead of the Java bloat customers.stream().map(c -> c.getName()).collect(Collectors.joining(", "))
59.
by still_grokking 10mo ago
Python's approach is one of the most confusing ways to possibly do it. Not having proper, discoverable methods is super annoying, and I need to look it up every time anew I use Python because it's so unintuitive. Of course you can
60.
by still_grokking 10mo ago
Scala is broadly used by the biggest companies in existence. https://business4s.org/scala-adoption-tracker/ The stuff currently cooking in Scala 3 will once more revolutionize the whole programming language landscape.

More ›