most hybrids run the engine for a few minutes a month anyway, as a precaution. keeps it lubricated and sloshes the fuel around to prevent it from layering.
also i don’t know how common this is but my car pressurises its tank to prevent offgassing, which apparently keeps the fuel good longer.
it’s not really about the type of data, it’s more about how you get it. web browsers could open gopher URIs for a long time, it was just a separate access method.
but the thing is, it doesn’t really make a difference today, because we’ve decided that http is some sort of base protocol.
someone decided to try making a custom matrix:// scheme (it’s called a scheme btw) for matrix clients and it’s just been a nightmare. clients don’t know what to do with the url, servers block it, we had to patch it out to get it to properly encrypt messages to our local homeserver. and matrix just uses http on top anyway.
no, i think they should be reserved for protocols that are important enough to be in the <1000 range of ports. like SSH, or Doom multiplayer.
back then? both codebases are fully modern. its more that sqlite uses a style that differs from the accepted norm quite a bit. that, and they don’t accept contributions.
fossil is made by the sqlite devs, for development of sqlite. this is not some amateur operation.
also, it’s by the sqlite people, so expect the code to be… odd.
well unfortunately desktop computers are kitchens, not restaurants. if you want a device purely for consumption, a pc is not the right choice.
sorry, apple already took that one. call it Jeff or something.
one method that helps is to not think of it as a workaround but as assembling a kit. the base system only comes with what everyone will need, and adding on an extra piece makes it more yours. that also helps with motivation to do a good job of it.
that’s switchable graphics for you. nvidia refuse to spill their secret sauce so all the effort in supporting that over the past 10 years have been clean-room reverse engineering. the only way it will ever get any good is if nvidia does it, or if they open it up.
i have always interpreted it as you cannot block signals that will break you. like if the us military drops an emp on you, you can’t design for that.
now that i type it out i realize how weird it sounds though.
Industry “conventional wisdom” often argues that FCC requirements somehow conflict with the software right to repair. SFC has long argued that’s pure FUD.
i mean, it is at conflict with right to repair. having to accept harmful interference to be certified means that repairability suffers simply because the device needs to be made to break.
you know, that’s a good reply. i wasn’t really opening up for discussion with that phrasing. should probably think a bit about how i write.
i’ve had dynamic lock screens available since my 2010 HTC desire… don’t really see how that’s new. absolutely ruined the battery life so i never really used it but it has definitely been an option on every phone since.
as for llms in phones, i will do everything i can to keep them out. if the npu chips were open and had published apis it would be a different thing. as it stands now it’s just a black box data vacuum that can tell jokes.
i had the misfortune once of having to try to understand a >400kLoC python codebase in a critical position and let me tell you that maintainability is a Problem. the system was older than most of the best practices of today and had a structure i can only describe as “a duolith of sqlalchemy soup”.
Bing Crosby
asking questions like this is how i found out that one of the allowed characters in names in my country is ÿ, which is fine in Latin-1 but in 7-bit ASCII is DEL.
it’s weird that. it’s obviously possible to have a flat-shaded skeuomorph, just look at basically all of windows 95, but for some reason we connect them to this particular graphical style. files and folders are both part of the old classic “desktop metaphor”, so they basically have to be skeuomorphs. but like, the application icons are basically just mosaic tiles of the normal icons.
a proper skeuomorph would indicate what the program is for. krita and whatever map software that is are both good, if a little flat. but the libreoffice suite just being squares with a letter on them? have them be like, a spreadsheet for calc, a stack of cards for impress, and a printed page for write.
remember all the icons for windows 95 network utilities that have people in them? those are also (attempts at) skeumorphs because they’re trying to communicate what the program does.
a skeuomorph (from greek, “tool/container-shape”) is something that retains the characteristics of another thing that it is based on, even though those characteristics are no longer useful. think lamps shaped like candles, or the floppy disk save icon, or media player programs with volume knobs.
skeuomorphic UX is a good way to get users comfortable with a system by using designs they are already familiar with, and the original iphone used this to great effect.
This is a good example of skeuomorphic UI:
all to say, I’m not entirely sure these icons are skeuomorphs. they’re just glossy.
it looks sort of like a continuation of the beaker browser project. basically, a peer to peer browser that also serves content you have made to others using the browser. it’s a cute idea.
Tom Scott of all people did a bit of speculative fiction on the topic “what if the first AGI isn’t the one made by scientists” six years ago. it’s a more classic paperclip maximizer story, but interesting nonetheless.