lemmyvore @ lemmyvore @feddit.nl

Posts

15

Comments

2,750

Joined

2 yr. ago

I mean, the process is not dying in either gif, so...

It stops working occasionally but they release fixed versions pretty fast.

Also, it's established practice for workers to stagger their off days across the week.

This way both the company and things like services, banks, stores etc. can be available 7 days a week without any undue pressure.

So they're already well positioned to take advantage of flexible working time.

Isn't it fourth?

Mozilla has already shipped strict privacy mode by default in recent versions of Firefox so they're already a leg up on this.

Google is currently trying to transition people to its own proprietary method of tracking (where the browser itself tracks you) so they would love it if third party cookies were no longer usable for that.

Mozilla has also added a direct tracking feature (anonimized) to Firefox btw. Not sure what their agenda is.

Websites are irrelevant, if third party cookies stop working in major browsers there's no point in setting them anymore, they'll be ignored.

Bayesian filters are statistical, they have nothing to do with machine learning.

Looking through the packages available for OpenWRT I would suggest Tcl, Lua, Erlang or Scheme (the latter is available through the Chicken interpreter). Try them out, see what you like.

I've actually tried using PHP on OpenWRT and embedded before. It's not exactly lightweight, it's a memory and CPU hog. Keep in mind that the kind of machine that runs OpenWRT might only have 32 or even 16 MB of RAM to work with.

Also, PHP is not the first language that comes to mind when doing data processing and/or functional programming. You can but it doesn't lend itself well to it.

You should consider if you really want to integrate your application super tightly with the HTTP protocol.

Will it always be used exclusively over a REST-ful HTTP API that you control, and it has exactly one hop to the client, or passes through hops that can be trusted to never alter the HTTP metadata significantly? In that case you can afford to make HTTP codes semantically relevant for your app.

But maybe you need to pass data through multiple different types of layers and different mechanisms (socket protocols, pub-sub, file storage etc.) In that case you want all your semantics to be independent from any form of transport.

It's a perfectly fine way of doing things as long as it's consistent and the spec is clear.

HTTP is a transport layer. You don't have to use its codes for your application layer. It's often done that way but it's not the only way.

In the example above the transport layer is saying "OK I've delivered your output" which is technically correct. It's not concerned with logical errors inside what it was transporting, just with the delivery itself.

If any client app is blindly converting body to JSON without checking (at the very least) content type and size, they deserve what they get.

If you want to make it part of your API spec to always return JSON that's one thing, but don't do it to make up for poorly written clients. There's no end of ways in which clients can fail. Sticking to a clear spec is the only way to preserve your sanity.

Endeavour differs very little from Arch once you're past the installer. To the point I've never understood why it's a standalone distro instead of an optional Arch installer, as an alternative to/part of archinstall.

They buy the hardware once then sell services based on it.

Oh definitely, Manjaro is all about "mommy knows best". It's why people who say "you should use Arch instead of Manjaro" are completely missing the point.

Technically, Manjaro used Arch exactly as intended, leveraging its flexibility, but it's very ironic that it used it to remove said flexibility. I'm guessing it's why some Arch fans feel betrayed and hate Manjaro.

Yeah you don't want your computer to be stable for 5 years going, that's very un-Arch.

Hilarious.

I like to call it Arch for the lazy.

Because AI reversed the ratio.

It's much worse. Generally speaking projects in large corporations at least try to make sense and to have a decent chance to return something of value. But with AI projects is like they all went insane, they disregard basic things, common sense, fundamental logic etc.