Yeah, but there’s also no way anyone in the Nordics would be fine with a nine-hour workday. There’s something clearly wrong here.
I’d rather guess that they’re working a five-day workweek but have cut the hours per day from 8 to 7.2, or 8 hours Mon-Thu and 4 hours on Friday or the like. The article just comes off as weird.
There’s nothing probable about the combination of a Nordic country and a 9-hour workday.
How does a 36-hour workweek work out to a four-day workweek?
Here in Norway everyone in sneezing distance of a union deal has a five-day workweek at 7.5 hours a day, for 37.5 hours in total. (The law says six days at 8 hours; the half-hour difference is in practice lunch, which is your own time with a union deal and the boss’ time without. I think we could go down to 7h a day and get an hour of lunch like our neighbours.)
No, we shouldn’t, and yes, you’re overthinking, but I am finding myself inching closer to the GNU argument for the desktop/server OS, as I now not only use phone/Linux, but also a bunch of Kubernetes/Linux, with distroless images. It’s all using the Linux kernel, and possibly glibc, but it’s not Linux as we know it. The desktop/server OS meanwhile might not have GNU coreutils in some years.
But realistically we’ve been using Linux as the name for the family of desktop and server OS-es for decades now, and if you need to refer to the Linux kernel you call it “the Linux kernel” or just “the kernel”.
Earlier GNU wanted HURD as an alternative to the Linux kernel—same GNU OS, different kernel. What instead is happening is that we’re keeping the Linux kernel but replacing the GNU part of the OS.
Generally you just need to give as much information as the recipient needs to understand your message. Excess signals that don’t add information are what information theory calls noise.
It’s also likely a bit of cost-benefit analysis for self-hosting vs using a managed service.
Codeberg would be more in line with Mozilla’s ideals IMO, but GitHub is a pragmatic choice anyway.
Phabricator was an alternative for a development platform of sorts; development ceased in 2021. They’re still running here and there, but I expect them to be in the process of being deprecated.
Må innrømme at jeg ikke er kjent med uttrykket. Er det en dansk eufemisme for tysk?
Yeah, some genres have a large segment of people who struggle to fit in with the mainstream. I’d like to think that they pick up something about social liberalism vs traditionalism from that, but there’s apparently also a significant segment who want as strict traditions as the mainstream, they just want somewhat different traditions.
Itt’s æ fønn mim, bøtt Ai ålwejs fil lajk thej kudd hæv dønn æ better dsjåbb åv the juropien spelling. In eni kejs, itt’s æ veri nais søbreddit, æn Ai kip fårgetting iff ther’s wan ån Lemmy.
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.
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.
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:
dict[str, Any]; most of us want the typechecker to help us write correct code.get from a map is Optional; you need to be constantly checking and handling that rather than being able to have methods that return T, or even direct field accessUltimately 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.
If you set up ruff you should get autoformatting (and you can enable various lints).
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.
I think it’s far more likely that the article that doesn’t know what “sweep under the rug” means also got other stuff wrong.