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:
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.
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, and those aren’t tied to a comment or anything it’s harder to make an opinion of our own. But for the communities I mentioned there are visible comments, and … I think OP wouldn’t have a good time at lemmy.ml, hexbear or blahaj, or even any instance where some common decency is expected.
Yeah, looking up the modlog for Lembot_0001 on lemmy.ml it seems there was more going on than just upvotes, and they got in trouble with programming.dev, europe@feddit and more as well.
if the process is just “wrong, do it again” without examining any piece of it
that’s the definition of vibe coding. It’s a process where you’re supposed to work as if you don’t know how to code and treat the code as magical mumbo-jumbo.
no, my point is that “vibe coding” is explicitly about not using your head and just going by “vibes”. It’s innately an excuse for shit code, because you’re not supposed to look at the code at all.
If you’re looking at the code and reviewing it, you’re not doing “vibe coding”.
I think you’ve mistaken me for some LLM slop enthusiast. I’m not.
Encourage “vibe coding” and you’ll drown in slop and ignorance.
Yes it is? That’s exactly what it is
IDK, I’ve mainly used the lspconfig plugin and haven’t really had problems in general, but some LSPs seem weaker than others
No, “not releasing them until they’re treated” just won’t fly. We have a lot of discussions about the loss of freedom in healthcare, and generally we can’t do something like that unless they’re an immediate danger to others or themselves.
Once they’re very sick there are a variety of treatments one can try, but they’re neither a replacement for social housing for people who are just struggling economically, nor something to deny people who need to get a return to normalcy.
It is also socialism, or at the very least social democracy here in the Nordics, and it works well :)
It turned out to not change much in practice for end users I think. We still want the lspconfig plugin for default settings for the most common LSPs, but setting up without it should be more straightforward. The lspconfig plugin will also be transitioning to the new configuration method.
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.