Nonprofits can “own” for-profits.
One of the saner reasons for this structure is that the non-profit owns the things the for-profit works on. If the for-profit goes under, all things are still owned by the non-profit, so some large tech company can’t swoop in and yoink anything available.
This includes any and all data generated by the for-profit, which means your data is “safe”.
Soon, Firefox can block ads better than Chrome. Ads are annoying. I see Chrome losing at least a 5% of the market, if not more, to Firefox, just because they’re going to break uBlock Origin, and Firefox isn’t.
Oh wow, looks like the Haskell devs have been hauling ass! Nice!
I remember the language server being a thing already, but it was in some alpha stage back then. Good to know it’s usable now! :D
Here’s what I remember from Haskell (around 2018):
I love the language, but hate the tooling.
Used it for Uni (did a minor where I learned Haskell, recursion, parsing and regex - probably the most information dense part of school I’ve ever had. Half a year of minor also burned me out, so I never went for my masters; I’m OK with my Bachelors :D ), but never felt like picking it back up.
https://en.wikipedia.org/wiki/Serial_port
Because there’s going to be kids around here who have never seen this port (other than maybe on a Point Of Sale (POS) system?)
I hope you can install Firefox, because The Googs is pushing for Manifest v3, which means no more functional adblock.
Linux or bust, babyyyyyy
I’m confused why you’re asking for feedback. You already chose Svelte and Sveltekit, no?
Here’s my feedback anyway: I like Python and dislike Javascript. Yes, Python is slow (though that can be offset via Pandas, among other libs) but it’s relatively painless. Unlike JS, which is quite painful to work with. JS libs also come and go every few years, whereas Python’s seems a bit more stable in that regard.
But it also depends on whether I’m part of your target audience - who is your target audience?
Also, regarding better formats: parquet is relatively nice. Smaller files, though not human readable. Use parquet if you read often, or have IO issues (file “too large” as CSV).
What’s even the “gold standard” for logging stuff I guess?
structlog. Or just Structured Logging in general.
Don’t do:
logging.info(f"{something} happened!")
But do
logging.info(“thing-happened”, thing=something)
Why? Your event will become a category, which means it’s easily searchable/findable, you can output either human-readable stuff (the typical {date}, {loglevel}, {event}) or just straight up JSONL (a JSON object/dict per line). If you have JSON logs you can use jq to query/filter/manipulate your logs, if you have something like ELK, you can insert your logs there and create dashboards.
It’s amazing - though it may break your brain initially.
I see an Arjan video, I upvote. This guy really boosted my Python knowledge during my Junior years.
That includes lemmy, right?
Right?
Doesn’t MANIFEST.in specify which other-than-the-known-package files and folders to include?
I bet you need to add them to the MANIFEST.in.
I use poetry, so I don’t need the MANIFEST.in, but I used it use a setup.py a few years ago, which is why I somewhat know of it.
https://packaging.python.org/en/latest/guides/using-manifest-in/
OK, but why would I use this over ABCs? (Abstract Base Class). Or is it just different?
Even their RDBMS and SQL was copied from ideas that came from IBM. And I recall either E. F. Codd or one of the SQL guys making a remark about Oracle’s less-than-saviour sales tactics, even back in the 90s.