Same in Oslo
syklemil
Also not having used Java for decades I'll not comment on the state of their abstractions, but
IMO at the extreme being unable to shed the past means negatively hindering progress. I think modern Java versions show a budding shift in mentality
both reminds me of similar complaints against C++ (and with a sizeable amount of users wishing for an ABI break), and how weird it is to get both complaints like that and over the fact that so many shops are on ancient versions. They've moved slowly, but it doesn't seem like anything was slow enough for a lot of shops, which indicates they likely could've moved faster without changing which versions users would be at today.
At the user level they're just tools, not programming languages. Python users are generally moving to ruff
(and uv
) because of ergonomics: It works well and really fast which makes for a smooth experience in-editor. Plus using fewer tools to achieve a similar result is generally desirable.
And for a complete newbie like someone taking a course, I think there's no "sticking with" to speak of. Might as well just skip over the tools people are migrating away from and start with the tool people are migrating to.
The price stuff can change through taxation that makes new plastic more expensive than recycled plastic.
As we all know, taxation is super popular and has never been controversial, ever.
At the very least flaskepant has worked great for like a century here in Norway. Always kind of surprising when other countries don't have it.
This sounds like the antithesis to parse, don't validate. It is possible to use just maps and strings and get a "stringly typed" program, but there' a bunch of downsides to it too:
- your typechecker can't help you if you used the wrong
dict[str, Any]
; most of us want the typechecker to help us write correct code - there's no public/private
- everything you
.get
from a map isOptional
; you need to be constantly checking and handling that rather than being able to have methods that returnT
, or even direct field access - you can derive or hand-implement a bunch of operations on (data)classes that you can't on maps: Comparison, ordering, hashing so you can use the blob of information as a map key, …
Ultimately while Hickey has a good point in the distinction between easy
and simple
, his ideals don't seem particularly aligned with the programming world at large: For one thing, Clojure remains pretty small, but even other dynamic programming languages like Javascript and Python have been moving towards typechecking through Typescript and typing in Python.
Doing a json.load
into some dict[str, Any]
is simple, but actually programming like that isn't easy. Apparently a lot of programmers find value in doing the extra work to get some stdlib or pydantic dataclasses. Most of us get a confidence boost from using parsed data, and feel uneasy shuffling around stuff that's just strings and maps.
It seems to run fine. You should likely as a TA or something as this appears to be something specific to your environment.
There's no null
in Python. There's None
, but like the other comment points out, just using return
is fine.
Yeah, the left generally considers it a "fighting day" similar to March 8th. The right does gardening (to make it visible that they're not marching). Others do whatever they feel like; not uncommon to spend the day hung over.
Yeah, one problem here is that global container circulation needs to, well, circulate. People don't ship empty containers, that's stupid expensive. So container hire is going to get way more expensive as global shipping needs to rebalance. Happened under covid, too.
Maybe just the waffle cracker? Because he's sprø som en kjeks, which works translate as … mad/cracked/crispy as a cracker?
Yeah, I think my sway config is around five years old now. The Wayland experience hasn't been entirely without warts, but as someone who kind of just uses the desktop to drive a browser and a bunch of terminals, there's not a whole lot of problems to run into either.