This on the other hand happily pretends to match any kind of realism requested like a skilled painter would, with the tradeoff mainly being control and artistic errors.
9,034 karma · joined January 12, 2017
This on the other hand happily pretends to match any kind of realism requested like a skilled painter would, with the tradeoff mainly being control and artistic errors.
The boot theory is different: It is about buying something not crafted with proper materials which will quickly fall apart and cost more in the long run. However, unlike technology, there is no cowhide 2.0 coming out 6 months after, with all leather made the cowhide 1.0 way instantly dropping in value and fading into irrelevancy.
Low-end laptops tend to be build around older SKU's which are no longer of interest but function no worse than they did when launched, and mid-tier laptops tend to be made with current SKU's in the more reasonable binning categories.
At the same time, the replacement rate also means that whatever high-end laptop will soon have its rear handed to it by a mid-tier machine of the next chip generation. While it's outdated within a year or two you of course won't replace it that soon, but that upgrade might stretch your upgrade schedule 50% to justify it - from, say, 4 years to 6. More years of being generations behind.
Keeping a Framework around for longer also only makes sense when considering upgradability.
> A case in point: at work we have HP Elitebooks. The brand-new 2025 models I see people receive have worse screens and trackpads than my 2013 MBP
HP Elitebooks are expensive, high-end machines. The issues you see is because HP, Dell and Lenovo all cater to IT department buying strategies, and therefore all offer a bargain screen option as the machines are bought in bulk and mostly used docked. You'll find that they also have an mid-tier screen option (usually a color-accurate 1080p or 1440p panel), as well as a high-end option (say, 4k OLED touchscreen with wacom digitizer).
The trackpad is a different story entirely. If you're used to a Mac trackpad, things are a bit grim on the PC side. There's some nice ones coming out though.
> They also degrade from daily use: the screen hinge loosens so it moves if you look at it wrong
Everything degrades from daily use. My hinge loosened on my last Mac, the screen damaged itself because the 15" panel did not have the necessary rigidity to main the intended 0.5mm gap to the keyboard keys (confirmed as the second panel did the same), the shitty magsafe port overheated as using pogopins for high power transfer is a terrible idea, all I/O on one side died, and the battery had inflated at least once...
My Dell XPS 13 costing 1/3rd never had any problems, and when replaced it just felt a bit slow and had a somewhat aged battery.
Price is not an indicator of quality or expected reliability, nor is the brand itself a reliable indicator. Use common sense, take a look at the product and avoid the bottom of the bargain bin.
---
Do get a good mouse and keyboard though, it has a much more direct impact on your user experience and a mouse that costs twice as much isn't as much of an issue as a laptop costing twice as much. The keyboard and mouse also lasts longer if kept well.
Buying and repairing a framework is never going to be cheaper than going through consumable trash laptops, and buying top of the line laptops and trying to use them longer is never going to be cheaper or better than buying medium grade laptops and upgrading more often.
What you're paying for right now is the customization capabilities and the ideology. Upgrading and customizing a single platform with a community, vs. a fixed one-off design that'll be lost next time you upgrade.
If Framework isn't already compelling to you at this time, then you're not the target audience. They might drop in price, but they'll never win a race to the bottom.
This should not be mistaken as appeal to authority, it is merely reasonable discrimination between those speaking from experience, and those forming opinions without experience.
If one believes those with experience has poorly informed opinions, they're always free to gain experience and associated perspective. They will then either have the fundamentals to properly push their viewpoint, or end up better understanding and aligning with the common viewpoint.
Assembly is not about corresponding to exactly which gates open when in the CPU. It's just the human writable form of whatever the CPU ingests, whereas C is an early take on a language reasonable capable of expressing higher level ideas with less low-level noise.
I seriously doubt anyone who has written projects in assembly would make such comparisons...
Can be a pain to move the whole suite to a new major (porting all their inhouse apps, getting all the hardware enablement from vendors updated to match, ...), but we're not dealing with a major upgrade here.
A security patch is "just" a matter of taking the last release, applying the diff, build, qa, release. No customization.
In the EU, neither would any American pickup truck: If registered as a normal class B vehicle, the total gross vehicle weight would be limited to 3500 kg (7700 lbs), and it would at most be permitted to tow 3500 kg (7700 lbs) with full independent trailer brakes, 750 kg (1650 lbs) without. You can add roughly 1000 kg if you tow a semitrailer, but getting the vehicle certified with a fifth wheel would probably be infeasible.
It doesn't make sense as a class C truck here (special driver's license, tachograph requirements for commercial use). It's way less nimble than our Scania/Volvo trucks (their turning radii are way tighter, and and have much smaller footprint for a given capacity), and is obviously a lot less capable than a vehicle that can be build from small utility up to the ~100k lbs range.
At the same time, if a farmer is outside the scope of a regular personal vehicle, they're most likely going to use their go-to tractor (e.g., Lamborghini, John Deere) which can haul anything anywhere, otherwise if they really need to haul they'll be reaching for a Scania/Volvo.
(It is common to register smaller, 7500 kg class C vehicles, but that's usually stuff like large Mercedes Sprinter vans, often built up as specialized service vehicles - think sewer inspection and repair.)
In the context of the US: It might seem like the best choice given the common options there, but I think the issue is with the options and perceived utility. It's the same with large trucks: The common ones in the EU are much more powerful, rated to haul more, are more comfortable, safer, have much smaller footprint for the given load and turns on a dime compared to US options.
A filesystem is by itself just one big "file" acting like a file archive.
Source: I live here and see it every day. Family, friends and customers are doing it, plus many eons ago I too was a tradesman driving home every day in the company work van.
(Heck, many companies wouldn't even have a place to park all their company cars at once, many such smaller companies run out of regular residential buildings with no dedicated parking.)
There's plenty of variation as they're all custom, and as they are work vehicles there should be plenty of cheap used ones on the market. The bed is also just a plate bolted to a steel frame so you can do whatever you want with it easily - adding custom boxes underneath, built-in ramps, changing the floor, whatever. They're also available with tall roofs with openable soft cover.
But as others suggest, used closed vans are also cheap and quite spacious, and on the big end you have the usual choice of a long-body sprinter which could probably fit 3 motorcycles inside with space to spare, with a much lower ramp height needed to get them in/out. Look around - it might not be as sexy, but there's definitely something that fits your need.
A standard mercedes sprinter in van configuration is 2020 mm wide without mirrors, which is as wide as the RAM and just 10mm narrower than the f150. I suspect the sprinter has wider mirrors, but I don't have the F-150 numbers to compare to so I'll leave that unanswered. Pickup configurations of the sprinter go much wider (and have extended mirrors to fit) - a common compact pickup bed configuration has a 2030mm internal bed width for example.
Note that the F-450 Super Duty is not applicable to the discussion as it won't work in the EU: A standard vehicle (class B) has an upper weight limit of 3500 kg. The F-450 Super Duty would have to be registered as an actual truck (class C), which requires a different drivers license and the use of a tachograph to track all driving and adherence to resting period rules. We don't use those vehicle classes unless strictly necessary.
As you say, they are absolutely terrible for work use as well - Japanese kei trucks famously have larger beds than some common US pickup trucks, and the size of the custom beds we use in the EU makes the US ones look like absolute kids toys - but that too I wouldn't mind too much if they were just forced to be safe and with decent emissions so the idiocy mainly affected the driver and their wallets.
I'm not too impressed with your vehicle only getting twice the gas mileage though. I'd expect more than that. :P
It's the norm in many businesses for employees to drive their work vehicle home and park it where they live, so they're everywhere. Not as many as regular passenger cars of course, but you'll see them on any residential road. Gardeners, plumbers, electricians, delivery services, this is the norm for all of them (a perk of sorts). Even big name-brand logistics companies, as it's common for the drivers to be independent contractors owning the van themselves so home is the only place to park.
They are also used for errands. They're legal for private use proportionate to the amount of VAT paid irrespective of registration type here, so you'll see them pick up/drop off kids, do groceries, recycle bottles, etc. in such vehicles too. Pretty sure that would be just as legal where you are given familiar EU rules.
For example, a Mercedes Sprinter in the standard long box configuration (as is used by local grocery delivery services, plumbers and the likes where I live) is 7.4 meters long , way longer than even the longest American pickup trucks (for some of them, several meters longer!), and is just as wide as them.
In custom box or pickup bed configuration (used by e.g., gardeners), these vehicles get wider (and sharper).
The tall grill means impact to pedestrians, bicyclists and motorcycles is basically instant death as their head - the only thing above the grill - gets whiplashed onto the rigid tip of the hood. On a normal vehicle you get your legs swiped and rotate your whole body onto an intentionally flexible area of the hood for a much gentler impact.
The visibility from the driver seat is not only much worse than our actual semis, but also worse than actual tanks. You could have half a kindergarten and a small vehicle in front of your car without knowing.
As for the tax, eh - tbf these vehicles are mostly used for business purposes by sole proprietors and the likes, and while they're stupid vehicles they do still do the job. A fully decked Iveco Daily or Mercedes Sprinter is also expensive with little registration tax. Registration tax is a weird (and arguably stupid) system, this isn't really an outlier in that regard.
I roll my eyes more when I see a sports car attempted registered as a van.
Also https://wayland.app to see the current Wayland protocols (the Wayland core protocol is mainly some common primitives, most stuff is across the other protocols). For example, the sync object stuff is in https://wayland.app/protocols/linux-drm-syncobj-v1 (in many cases handled by your toolkit or WSI of choice).
That is still just a normal VM, but it's nice that it's automated.
> enabling the installed video card to accelerate graphics within X and/or Wayland.
nit: X and/or Wayland is not involved in application rendering at all - its applications themselves that use the GPU and its acceleration directly.
Wayland and/or X is only involved when the apps are all done rendering[0], and the display servers own rendering is the comparatively simple task of stitching windows together[1], and sometimes not even that.
0: You can send buffers early over Wayland if you also send a sync fence, but this is just forwarded as a render dependency that the GPU scheduler will patiently wait for.
1: well also dealing with stuff like color transforms which can be complex to understand, but are computationally cheap and for fullscreen content possibly entirely free.
While your base64 attempts likely went well, that it "could consistently encode and decode even fairly long base64 sequences" is just an anecdoate. I had the same model freak out in an empty chat, transcribing the word "hi" to a full YouTube "remember to like and subscribe" epilogue - precision and determinism are the parameters you give up when making such a thing.
(It is around this time that the models learnt to use tools autonomously in a response, such as running small code snippets which would solve the problem perfectly well, but even now it is much more consistent to tell it to do that, and for very long outputs the likelihood that it'll be able to recite the result correctly drops.)
Same happens with regular people - a smart person doing something stupid because they weren't overly critical and judgingof your request - and these tools have much more limited thinking/reasoning than a normal person would have, even if they seem to have a lot more "knowledge".
Same with asking a person to solve something in their head vs. giving them an editor and a random python interpreter, or whatever it is normal people use to solve problems.
Hmm, the Go GC is really quite capable, so I wonder what kind of pathological load it was being presented with. Even then, when the GC "fails" it means elevated CPU load from collection.
The main thing I can think of would be the application "leaking" by having unintentional references (or worse, actually leaking through cgo bindings), or trashing the allocator to cause temporary spikes in between cleanups.
However, while I don't think Go was actually to blame here, I would never use native UI bindings to a language that isn't 1:1 compatible with the original design and memory management principles, as such bindings get disproportionaly large and complex. It just sets you up for a bad time.
Neither Apple nor Google is doing anything revolutionary with their silicon for such a standard compute task. It's really mostly minor tuning to get a more optimal part instead of an off-the-shelf chip catering to other uses too, with die area and power consumption "wasted" in your setup.
The screens are a good point, but nothing about LED headlights require a single bright point. That's done for style and cost saving - old reflector headlights had to be big, so small looks "modern", and small means less material.
Cramming it all into one tiny spot just means cooking the LEDs, which are much better suited for either larger lens assemblies or multiple smaller lens assemblies to distribute the load, both of which increase the size of the light source and massively decrease the blinding and glare it causes. You could easily cut the glare to, idk, a quarter by just changing the geometry a bit while maintaining the same light output.
It's a little gross it had come to that, but ugh. Sure rebble did good for the community, but that past tense is important. Now they're trying to do bad, and that cannot be justified. Accusations require a defense, so here we are.
The Pebble community is not and never was Rebble. I briefly used Cobble as an open source project, and used their app store mirror that they decided to host to download the same old apps and watch faces I used while Pebble lived, but I was not using a Rebble watch. The open source apps I want were never Rebble apps. No one expected Rebble to be anything than infrastructure life-support, but as no one thought the dream of new life in Pebble was never going to happen, it was the light we swarmed.
Now the life support task has ended with an appreciation for their efforts, and Rebble starts acting like a company running a smearing campaign trying and make up IP ownership and justification for royalties.
Rebble no longer represents any of the community, just a misguided and greedy board. What the community wanted now exists, so that is where we have gone.
Pretty much only search-specific modes (perplexity, deep research toggles) do that right now...