I'll still pick up litter when I'm walking through a rich neighborhood, even though those people have groundskeepers to take care of it for them. No one is doing this with the goal of a profit.
1,700 karma · joined January 9, 2021
I'll still pick up litter when I'm walking through a rich neighborhood, even though those people have groundskeepers to take care of it for them. No one is doing this with the goal of a profit.
Far more will die due to other kinds of pollution it emits, and an unknowable number will die due to the effects of climate change caused by CO2 emissions.
But when a few hundred people, or really just 0 people[2] die in one place at one time, people lose their minds.
[1]: https://www.theguardian.com/environment/2023/nov/23/coal-pow... [2]: An inter-agency analysis concluded that the accident did not raise radioactivity far enough above background levels to cause even one additional cancer death among the people in the area https://en.wikipedia.org/wiki/Three_Mile_Island_accident
I imagine it's similar to what we see in software, where we see mega-waterfall projects delivered for the government cost way too much and still fail, and where tech companies & literal hobbyists can deliver higher quality software more quickly by avoiding an overbearing planning process.
Now there's no such concept as a ganged/unganged state. You move the middle (which has the larger area, since it's the most common tool) to move them together, and the side sliders if you want to control thrust individually.
The unpublish document describes the options that users of NPM have to remove packages themselves. It was created after some situation where someone unpublished an important package.
A whole different set of terms governs which packages NPM can remove. This definitely includes these packages, either as "abusive" or "name squatting"
Not only that, but NPM's TOS makes it very clear that you have no recourse if they decide to remove your package for any reason.
The concept of supply & demand shows people obviously do want this, given that the cost of living in that walkable city and in walkable places is so high.
The real reason? Americans become infatuated with the latest technological marvel too easily. For a while, this was the car. And unfortunately, rolling back all these car subsidies takes a while and is heavily fought against because people hate the feeling of having something taken from them.
https://i.imgur.com/9MYqLvj.png
I can quickly disable XHR to confirm websites don't do anything server-side when I don't expect them to.
> "is my specialized datastore gonna be faster than Redis"
Absolutely! With how efficient this code would be, you'd likely never need to scale horizontally, and in that case it is extremely easy to compete with a network hop (at least 1ms latency) versus L1 cache (<50ns)
The comparison with redis otherwise only applies once you do need to scale horizontally.
There's also the fact that redis must be designed to support any query pattern efficiently; a much harder problem then supporting just 1-2 queries efficiently.
I mean this is basically your redis situation right? Just with a very specialized "redis".
You could scale this out, even after the pretty massive ability to scale up is exceeded. Have some front-end servers that act as a connection pooler to your datastore. Or shard the datastore, and have clients only request from the shards that they are currently looking at.
The price is far far less than whatever the price of a human life is. The reason they are not implemented is not cost, but because people here consider it their god-given right to drive as quickly and aggressively as they want.
If you have some background knowledge of Google's architecture, this explains exactly why the AGPL is banned there: all code is built from one monorepo where everything is linked together.
> https://writing.kemitchell.com/2021/01/24/Reading-AGPL
This completely agrees with what I said. At it's core, the A part of the AGPL only kicks in if:
> “you modify the Program” and > “your [modified] version supports such interaction [remotely through a computer network]”
Yes he calls out various potential problems and a potential loophole, but those same problems are also present in the regular GPL!
> Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
> Does connecting a AGPL-licensed database to your website make your whole website AGPL?
The user doesn't interact with the database, so no. Since the app server is not linking to the database, it also isn't subject to the AGPL from that direction.
> What is the line between an innocent connection, or a viral integration?
Exactly the same as the GPL, since that section has not changed.
> What happens if you add a proprietary protocol to the database specifically for your app? Do you need to open source it, if that database is/isn’t publicly accessible?
If the user can access the database, you must provide them with the combined source code under the AGPL. If the user cannot access the database, you do not need to do anything.
> Why wouldn’t it be considered? Your project dependencies certainly aren’t directly publicly available, yet you agree the AGPL applies there.
You are linking against those dependencies. Therefore the whole work is under the AGPL, through the same mechanism as the GPL. Now that the entire work is under the AGPL, you must provide users who access it over the network the source code.
> Some have quoted the FSF about how “internal data structures” should be the distinction.
See this is a real source of ambiguity. But it is an ambiguity that applies to every *GPL license, not just the AGPL. But it's really not as big of a deal as you make it out to be, using the documented public network APIs obviously is not linking.
She doesn't get the memo that she isn't actually supposed to do anything and suggests poorly substantiated investments and potentially does a little fraud... exhausting just reading about it, I'm not sure why I bothered.
There's no real takeaways here except he should just keep it in his pants. Definitely nothing worthwhile for this audience.
I wonder if this is still the case. I took a WD helium hard drive apart recently and I think I saw just a PCB glued in place for the electrical signals. Probably made from very special materials, but it looked just like usual.
I'm not really sure I understand either, I've had this bootloader-free setup working great for quite a few years on my machines too.
> There's one glitch that occasionally confuses people. When the software lobs a story, it displays a rolled-back timestamp—not the original submission time, but a resubmission time relative to other items on the front page
So it would be better from this perspective to not have much buying & selling, as long as the most recent owner is trustworthy & has used the property for the past 7.5 years.
It's pretty bad, but not trivial to exploit, especially since most machines are 64-bit with a larger space for ASLR.
It's designed for an oval crimp around the insulation & a m-crimp on the wire. The typical cheap crimpers have two sizes of m-crimp, which is fine for a lot of JST connectors for example, but not this.
The IWISS SN-025 works well for the Mini-PV too. Which makes sense, since the dupont connectors are a near-clone designed for cheaper production.
> As a hobbiest you don’t recommend doing your own crimping at all
I just don't find it very enjoyable, especially getting to the point where I have tools that are actually suitable! The IWISS SN025 is fairly new[1] and before I ran across Matt's blog, reliable information on this subject was hard to find.
But I mean I have after all gone through the effort of getting tools and connectors, so it's more of a medium "recommend against" rather than a "not worth doing at all". It's almost like my preference with assembling PCBs. I don't mind that as much, and am good at it, but if I can just pay someone $20 to do it for me, I'll do that instead. Except I don't think there's any services at that price point for cable harnesses.
[1]: https://www.mattmillman.com/iwiss-sn-025-another-head-scratc...