get rid of companies making money off the FOSS

I'm afraid if we discourage companies from adopting open source we'll end up with even more closed source garbage.

There are industry sectors where closed source is the norm, and it just leads to more vendor lock-in and less standardization and interop.

I'm a bit young to say for sure, but I believe closed source was the norm in the software world 20-30 years ago and openness was stigmatized. I certainly don't want to live in that world.

doesn't look a day over 69

40 on each leg

it does work though, on windows i can see ads and intrusive crap all the time. Linux distros don't bother you at all, it's like linux is not even trying at this point.

you can be anything you want, bud, don't let them tell you otherwise!

That's the billion dollar use case for AI! Time to post it to shlinkedin.com

not enough linkedin

Engaged in an enriching 3/4 hour guided exploration of the prestigious Stanford University campus, which offered an in-depth look at the institution's distinguished landmarks and vibrant academic environment. (Was not accepted)

that should do it

nonsense, there are only 12 months

"oh no, anyway..."

GTA online was fun from 2015 until a couple years later before flying bikes and sky races. R* kept pushing updates that appeal to teenagers and absolutely ruined it.

this is what I'm talking about, Pete. It's for your own good. This obsession with gathering data has to stop.

as opposed to human-generated code

i cast str to int

tldr

1. Keep Commits Small: Ensure commits are small and manageable to facilitate easy reverts and debugging.
2. Continuous Refactoring: Prioritize frequent, minor refactorings to simplify future changes.
3. Deploy Continuously: Regularly deploy code to ensure it works in production, as working software is progress.
4. Trust Frameworks: Avoid over-testing framework capabilities; focus on application-specific logic.
5. Create Independent Modules: Place functions in new modules if they don’t fit existing ones, preserving code organization.
6. Write Tests Early: Use tests to design APIs and guide development, but don’t be rigid about TDD.
7. Avoid Duplication: Prevent repeated code by abstracting similar implementations after copying once.
8. Embrace Change: Accept and adapt to evolving designs, understanding that change is intrinsic to software development.
9. Manage Technical Debt: Focus on minimizing immediate blockers and plan for potential future issues.
10. Prioritize Testability: Ensure that your code and design facilitate easy testing to maintain code quality and coverage.

Scientists using macs connecting to servers and other machines running Linux.

Unknown share is high too; Linux usage on desktop in Antarctica could be as high as 15%.

valid question, idk why would people downvote it

broken websites on desktop are rare and not nearly enough to drive a browser change, but they usually fall into two categories:

1. websites that "break" on purpose for no good reason when they detect it's not chromium. Either avoid the site or change the user agent.

2. websites that degrade some functionalities because they rely on newer features or on how things appear on chromium. They're usually CSS breakages and do not affect browsing that much.

Support for manifest v2 greatly outweighs these potential issues imo.

top 5 best things I've done in the last year

mah man

those damn romans, man...

one month would need to be more flexible for the division remain and leap years, but it would I suppose.

It makes budgeting easier, for one. But it's just a really arbitrary way to have a measure when a week is too little and a season / year too much.

man man

oh man

no wonder it was taking long to load; it's a 58MB HTML file.

really cool stuff though - I'd love to see more information of what's on the screen:

• Number of postings (updated when filtered using the search);
• Some way to visualize posts in the intersection of these clusters e.g. Software Dev with Education; AI and DevOps.
• Word cloud of most common terms in the posting selection;
• Ways to export the filtered data.

they have moved, but I wouldn't call a 40" TV large for almost 10 years now.

so... people who take typing lessons and actively try to improve it have better typing skills than the ones who don't. Shocking.

Because you're assuming foo won't be renamed when it becomes a function. A function should start with a verb, say get_foo(), because just foo() tells me nothing about what the function does (or what to expect as output). If you make it a property, get_ is implicit.

So if the age is computed from the year of birth for example, it's really e.g. thing.age or thing.get_age() - both of which are fine, but I'd pick the property version.

I like it. Months are useful on Earth, but their absence in other planets' calendars will go a long way to simplify things. Seasons can remain a function of Sols with periodic corrections over centuries to account for rotational speed changes.

that we agree on: properties should be cheap to compute.

Making a simple ternary condition as a function instead of property is a wasted opportunity to make its usage cleaner.

Properties make semantic sense. Functions do something, while properties are something. IMO if you want to name something lazily evaluated using a noun, it should be a property.

Totally agree. The hardcoded isAdult: true repeated in all #2 examples seems like a bug waiting to happen; that should be a property dynamically computed from the age during access time, not a static thing.

I'm a native pt speaker and I had never thought of the word as slur. I remember it being commonly said on TV, music, and written on newspapers without this connotation. It was certainly more common than the preferred alternative "mestiço".

insert standards xkcd

what do you mean by one server per tool?

it ends when you become lunch

Exactly. A few months ago the headline was a patent of Roku hijacking HDMI to show ads.

I'll save my energy to be pissed off when this garbage actually makes it to market.

Learn a docker compose deploy. It's a knowledge that pays off for services other than jellyfin too.

I forgot pyright: it might be a good choice, but since you like strict mode, see basedpyright instead. I don't know about integrating it with emacs though.

I'd pick between Ruff and (based)pyright - maybe both if that works in emacs.

Ruff.

MS LSP is also deprecated in favor of Microsoft's pylance AFAIK. I've never used Jedi much, but it's one of the older ones and not very comprehensive to my knowledge. Ruff is relatively new but they already have >800 rules and increasing. Ruff is by far the fastest too.

No thoughts on py-lsp.

Ah, just be sure to enable most (or all) rules with ruff, as the default rule sets are pretty relaxed.

h and r are strings on creation:

type("5.00") # str
type(5.00) # float

I don't have a ~/.kde for a long time, but I did set my xdg dirs years ago too.

Collectibles are non-fungible tokens by definition, and blockchain is just a data structure.

I don't care about collectibles / NFTs, but this is nothing new in the gaming world.

since the data is tabular, JSONL works better than JSON for large files