To be fair, GCC's design was motivated by the same thing as the license. They intentionally didn't modularize GCC so that it couldn't be used by non-free code.
> Anything that makes it easier to use GCC back ends without GCC front ends--or simply brings GCC a big step closer to a form that would make such usage easy--would endanger our leverage for causing new front ends to be free.
> Why does there seem to be much more market for NAS than for direct attached external HDD?
I can access my NAS from anywhere in the world, but you can only access your direct-attached drives when sitting at your desk.
I can hide my NAS in a closet, but your direct attach drives are wasting valuable desk space and causing noise in your workspace.
My NAS has a software raid (raidz2) so any two of my drives could die without losing a single bit of data. Technically this is possible with direct attached drives too, but usually people aren't attaching multiple external drives to their computer at the same time.
Multiple people/computers/phones can access my NAS simultaneously, but your direct attach drives are only usable by a single computer at a time.
I can use my NAS from any device/operating system without worrying about filesystem compatibility. With direct attach drives, you need to pick a filesystem that will be supported by the devices you want to plug in to it.
The downside is a NAS is running 24/7 which will consume more electricity than drives you only plug in on-demand, and file transfers will be slower over a network than directly plugged in to your computer, but 99% of the time the speed difference does not matter to me. (It really only impacts me when doing full-disk backup/restore since I'd be transferring hundreds of gigabytes.)
You can configure a NAS to use Wake-on-LAN, so that it will not run 24/7, but only when you wake it up remotely. After you finish using it, you power it down remotely, until the next use.
No one is giving their IoT devices public IPv4 addresses. They would be behind a NAT. RFC 1918 provides 17,891,322 usable IP addresses for each private network. If we want to be a little more adventurous, RFC 6598 provides an additional 4,194,302 usable addresses and 240.0.0.0/4 is another 268,435,454 usable addresses "reserved for future use" since 1989, but still sitting unused so we can use them as internal addresses inside a NAT anyway (for example, AWS uses this range internally).
Show me a network that is using all 290,521,078 addresses and I'll show you a network managed by a team of network engineers who can just set up IPv6.
You still have to manage those and assign them through DHCP every time the device wakes up and turns the radio on. Maybe WiFi 7 will address that with the low power mode? Also, I don't want a 100 sensor mesh network on my LAN. That's why Thread uses a IPv6 6LoWPAN. One should use that if they want to bridge to IP.
I think the important distinction is _everything_ should be considered untrusted because even trustworthy software can become malicious. For example, the XZ Utils backdoor[0].
On Android, everything I run is subject to the permission model and sandboxed. That is not the case on Linux.
Could you be more specific on how to circumvent the android permission model + sandbox? So far I have only thought of two ways an XZ-like backdoor could circumvent that:
1. By being baked into the OS itself, which is unavoidable since the OS is the thing providing the sandboxing + security model. It still massively reduces the attack surface.
2. By being run through the android debug bridge, which is far from normal and something users have to explicitly enable. Leaving you the option to shoot yourself in the foot in an opt-in manner 99.9% of users will never touch isn't the same as Linux where foot-shooting is the default.
The defining aspect of the XZ backdoor was that it was baked into the OS itself, being linked into memory space by about half of the system and activated by being packaged in a specific way in a specific distribution. If you wanted to ignore 1), you would have to choose a different example.
If you want to confine yourself in a sandbox, feel free to do it. The past decades have demonstrated that it's only necessary for some specific threat models.
- create group: send an MMS message to whoever you want in the "group". Now you have a group chat.
- invite people: send a new MMS message including all past participants and the one additional participant.
- kick them out: Send a new MMS message including all past participants except for the person you want to remove.
- send messages + audio/video: MMS supports all of this.
MMS is the worst standard in telco and that's saying something. The spec is impossibly complex, so it's not properly supported by carriers or device manufacturers, and even basic cases like "send this photo" fail alarmingly regularly.
Yeah, I really tried to cover a part of how it's so bad in my post. It's really something from a different time. There's a lot of the old WAP 1.0 kind of thinking where the carrier ran their own proxy to make the content consumable by the end device due to limitations at the time. If you don't fetch the content off the MMSC in time it expires. I know there's lots of RCS spam complaints, but the carriers ran email to MMS gateways that had abuse for years.
Verizon had the wackiest system with their vtext service where it really tried to customize more than the GSM carriers and they ran their own web portal. When they phased that out a few years ago it broke picture scaling for pretty much all non-iphone devices on their network. This is another big reason I wanted working RCS because if I send a picture to Android users on Verizon it ends up scaled down.
It's the same thing. Just like how a "cash discount" is the same thing as a "credit card surcharge", the end result is the same regardless of how you word it. Simply stop using the first group. You can even be explicit by sending a message to the first group of "I'm forming a new group without Becky because she's a loser" or you can start the new group with a message "I started this new group without Becky because she's a loser" which has the added benefit of humiliating Becky as she keeps sending messages to a group that will not respond to her.
I don't know if you are purposefully being pedantic here, but they are very different things. Even as an adult who has been in several of these very active iMessage group chats with "mutual bullying", they are vastly different from any of the RCS/SMS groups I'm in due to some of the features in iMessage.
What are those features? I've never used iMessage but my ultimate point is that iMessage isn't enabling bullying, it just happens to be the platform these kids are currently using. The same bullying tactics have been possible since long before the iPhone existed.
So far semi-extrinsic provided a list of features they think is uniquely enabling bullying in iMessage but I've just established those features are actually commonly available to everyone, so what other features does iMessage have that uniquely makes it enable bullying compared to MMS?
I don't have an iPhone but surely you see how the UX is very different between:
(a) create new group minus Becky and minus all previous messages, plus every participant has to migrate over
(b) "admin" kicks Becky and no one else has to do anything and all the history and context is retained
I've been in plenty of MMS group chats where we've had to create a new group to add or remove someone (for non-bullying reasons) and it has always gone smoothly without issue. SMS/MMS apps tend to sort your list of groups by most recently received message, so as soon as people stop using the first group it will naturally decay to the bottom of your list where no one looks.
> "admin" kicks Becky and no one else has to do anything
"admin" creates a new group chat, no one else has to consciously do anything because they're just selecting the group that has the most recent messages and therefore is at the top of their SMS/MMS app.
There is one difference here in that with SMS/MMS there is no "admin" so anyone can create new groups, but if you're going to start evicting people without buy-in from the group then the dissenters are just going to form their own groups anyway regardless of platform.
> all the history and context is retained
That is a fair point, you wouldn't maintain the history/context but how important is that for bullying? My ultimate point here is that fastball is correct in that the iMessage platform isn't enabling bullying, it is just the kids preferred platform. We have all been perfectly capable of the same bullying since long before the iPhone existed, and I don't think losing history/context when forming new groups changes that.
I have owned a mobile phone since 1996-ish IIRC (Nokia 1610).
I have sent exactly zero MMS messages successfully. They've always failed on some stupid carrier setting being wrong. I've also "received" MMS image messages - that were links to a carrier portal because the image could not be delivered.
It's a shit standard that nobody bothered to implement properly =)
I've been making my reports in self-contained HTML files[0] and it works out so much better than PDF. It is not constrained by paper sizes, and it lets me add some nifty features. For example, I recently added support for hiding columns in a table using exclusively CSS. The only downside is browsers can render things slightly differently, but for my use cases I don't need pixel-perfect identical rendering.
[0] Images are inlined base64-encoded, CSS/JS embedded with style and script tags. No external assets / no http requests.
Being constrained by page sizes is “a feature, not a bug” in most contexts. If I’m calling out numbers on the 3rd line of page 38 of a report, it helps if that’s consistent.
The only reason PDFs still have a job is: pixel perfect consistency; the built-in validity stuff (ensuring the document wasn't altered, etc.); or the customer doesn't need the other things, but isn't open to alternatives. Otherwise, PDF is just a major headache.
Also page-level consistency, and generally layouting in a printable format
Even with the same word document opened only in various MS Word versions (web, desktop, etc) you won't get consistent page numbers. And HTML tables work great on screen but don't print very well if they span more than what fits on a single sheet of paper
Not only can you embed the fonts, but you can make it interactive and output a PDF if you really wanted to. The HTML might grow if you embed enough JS, but on the other hand... some PDFs are insanely large.
If you leave ground alone all sort of things grow on it or lay on it. Dirt, mud, leaves etc. Soil grows at about 1 mm per year. 1 meter in 1000 years.
Historically cities were hit by floods and wars and new buildings were built on top of the foundations of old ones. We had an article about that church in Rome built over another roman church built over another roman church, etc. down to an old temple on a spring, or something like that.
It might even happen faster than that. If I don't sweep my cement patio for about a month, the decaying leaves from the bushes are enough to make about an 1/8th inch of fresh brown soil under the leaf piles.
> Delgado received his first big assignment back in 1978 while working for the National Park Service: excavating and studying the remains of the Niantic, one of the first whaling vessels that brought gold-seekers to the area. It had been discovered near the Transamerica Pyramid at the corner of Clay and Sansome streets. After being left behind during the Gold Rush, the ship had been repurposed to serve as a storeship, saloon, and hotel until its demise in an 1851 fire.
Before industrial demolition was common, old buildings would be town down and material repurposed for new constructions, build on top of existing foundations and rubble. Do this enough over the centuries and your city will slowly rise in height.
If anyone’s ever in Barcelona I recommend checking out the history museum, which is literally built on top of some Roman and medieval ruins. You can descend into the basement to see the excavated remains of the foundations of Roman buildings that had been levelled and built on top of.
Tons of cities have hidden underground streets that are the old street level and now abandoned due to all manner of modernization.
Walking around Chicago I often see houses where the front door is a couple of meters below street level because the house never moved its door to an upper story when the city was releveled.
Every time a building fell apart due to earthquake, fire, flood, war, abandonment- the good material was taken for reuse and the bad material became rubble which was often smoothed out and used as a foundation.
That's already the case. I run a quantized 70 billion parameter llama 3.1 model on my framework 13 inch laptop. Only cost ~$300 to get the 96GB of ram (which I purchased for unrelated non-AI reasons before the AI boom). It certainly isn't fast, but it is fast enough. I run it via vulkan compute using llama.cpp with an anythingllm web interface in front of it.
Wikipedia puts the "preferred walking speed" around 3 miles per hour, so that would be 2 hours of walking per day. So with 8 hours of sleep, 8 hours of work, 2 hours of walking, 1 hour of hygiene, 1 hour of commuting, and 2 hours for meals, you'd still be left with 2 hours of personal time to do all your extracurriculars like cleaning, parenting, spousing, hobbying, shopping, repairing things, etc.
You are neglecting the optimizer approach of working while walking; etc. Also, hygiene during the commute - just shave and brush your teeth on the bus. And sleeping while bathing is a real time saver.
> you'd still be left with 2 hours of personal time to do all your extracurriculars like cleaning, parenting, spousing, hobbying, shopping, repairing things, etc.
In what way is parenting an extracurricular activity?
3mph is a pretty slow stroll - 5 or 6mph is more normal for purposeful walking on the flat - so it’s more like 1:10 of walking, which could take the form of a 35 minute walk somewhere, and a 35 minute walk back.
As for cleaning, repairing things, parenting, shopping - those are all things which can readily incorporate walking and physical activity.
> all routers are uniformly fucking awful [...] the world has become trained that rebooting a router once a week and praying that it works when it comes back is a perfectly normal state of affairs
My OPNsense router currently has 74 days of uptime, and that's just because I ran an update 74 days ago. I've never rebooted it to solve a problem. The only wrinkle is OPNsense (and pfSense) is at least an order of magnitude more complicated than your average consumer router.
OTOH, my ubiquity access point reboots itself every time I change any setting at all.
> Anything that makes it easier to use GCC back ends without GCC front ends--or simply brings GCC a big step closer to a form that would make such usage easy--would endanger our leverage for causing new front ends to be free.
https://gcc.gnu.org/legacy-ml/gcc/2000-01/msg00572.html