On "the actual
environment/background is not made of Lego" complaint:
while Bricktales looks neat, its "environment/background" is tiny.
For anyone interested in a more Minecraft+LEGO experience, with an actual world made entirely of LEGO that you can interact with, check out LEGO Worlds. (currently 80% off on steam)
Congrats, you've just discovered internet memes.
I don't share the hate for flat design.
It's cleaner than the others, simpler and less distracting. Easier on the eyes, too. It takes itself seriously and does so successfully imo (nice try, aero). It feels professional in a way all the previous eras don't - they seem almost child-like by comparison.
Modern design cultivates recognizable interactions by following conventions and common design language instead of goofy icons and high contrast colors. To me, modern software interfaces look like tools; the further you go back in time, the more they look like toys.
Old designs can be charming if executed well and in the right context. But I'm glad most things don't look like they did 30 years ago.
I'm guessing many people associate older designs with the era they belonged to and the internet culture at the time. Perhaps rosy memories of younger days. Contrasting that with the overbearing corporate atmosphere of today and a general sense of a lack of authenticity in digital spaces everywhere, it's not unreasonable to see flat design as sterile and soulless. But to me it just looks sleek and efficient.
I used to spend hours trying to customize UIs to my liking, nowadays pretty much everything just looks good out of the box.
The one major gripe I have is with the tendency of modern designs to hide interactions behind deeply nested menu hopping. That one feels like an over-correction from the excessively cluttered menus of the past.
That and the fact that there's way too many "settings" sections and you can never figure out which one has the thing you're looking for.
P S. The picture did flat design dirty by putting it on white background - we're living in the era of dark mode!
Love this comment.
Absurd, mysterious, unapologetic.
Extra steps that guarantee you don't accidentally treat an integer as if it were a string or an array and get a runtime exception.
With generics, the compiler can prove that the thing you're passing to that function is actually something the function can use.
Really what you're doing if you're honest, is doing the compiler's work: hmm inside this function I access this field on this parameter. Can I pass an argument of such and such type here? Lemme check if it has that field. Forgot to check? Or were mistaken? Runtime error! If you're lucky, you caught it before production.
Not to mention that types communicate intent. It's no fun trying to figure out how to use a library that has bad/missing documentation. But it's a hell of a lot easier if you don't need to guess what type of arguments its functions can handle.
It's almost like their class interests changed and class interests influence behavior.
Almost like it's proving their point. Capitalist critique is not about individual "bad" people but about a system with perverse and harmful incentives.
(granting your claim for sake of argument - feel free to support it with data)
I can't for the life of me figure out how your proposed method helps in the described scenario.
Maybe I misunderstood it, can you elaborate?
If you kept going for a few paragraphs, this might have turned into a decent copy pasta. Shame, really.
Yup.
Spaces? Tabs? Don't care, works regardless.
Copied some code from somewhere else? No problem, 9/10 times it just works. Bonus: a smart IDE will let you quick-format the entire code to whatever style you configured at the click of a button even if it was a complete mess to begin with, as long as all the curly braces are correct.
Also, in any decent IDE you will very rarely need to actually count curly braces, it finds the pair for you, and even lets you easily navigate between them.
The inconsistent way that whitespace is handled across applications makes interacting with code outside your own code files incredibly finicky when your language cares so much about the layout.
There's an argument to be made for the simplicity of python-style indentation and for its aesthetic merits, but IMO that's outweighed by the practical inconvenience it brings.
Yes, correcting hyperbole with relevant information is bad, actually.
It does and you can safely ignore us.
Just two pendants nitpicking people's spelling on the internet.