Re: its "ultra-hard stainless steel" [...] "transparent metal" [...] "literally bulletproof."
Can't believe nobody has said anything about pissing on the hood.
127 publicly visible posts • joined 19 Nov 2009
Plugging my android phone on my windows worl laptop and activating the usb tether creates a network device that claims 433 mbps. *Claims*, I haven't had a chance to verify that, since the 4g uplink was never faster than 50.
Might not be as fast as the latest wifi but it ain't bad either.
So in their opinion I come to the shop, install all the stuff required for the typical builds I do during the day, THEN complain that 8 gig aren't enough for my needs, when I know the builds will take more than that and memory compression can't get far enough?
"We are much more efficient in memory use", yes but zipping data has limits not even Apple can break and not all the software I use is written by Apple, especially that which is written by me, and making all the changes needed to be the best M3 native app, with the lock in that brings, is a bit much when all I needed was 32 gigabytes of RAM.
I fixed a 3.5 inch floppy drive with a similar application of sharp blades.
Brand new PC (tower case) wouldn't write or read fro floppy. Year about 2001. My uncle gave me a ring about it two days after he bought the thing.
Much messing about looking for loose cables, at some point we had the thing on with the case open and its front off. To our surprise, floppy worked fine. Front back on, floppy failed again.
The front had a plastic facade in front of the floppy and a thingamajig to allow the operator to push the eject button on the actual drive. The thingamajig was about two millimetres too long and would keep the button half pressed when the front was screwed on. Snip snip and all was well.
When I told my dad I wanted to study computer science, he said: but why? The things have been built already.
Same as "Write it right the first time"
Funnily enough, in his daily job* he was very well acquainted with "needs change, things get old, stuff breaks". He'd even joke half his work was fixing the stuff he'd built twenty years before. Microsoft has just made a business that ensures things break at scale, instead of at their usual pace.
* he was a plasterer before retiring
Fine grinding? Remote location? Waste of energy.
Chuck them in a spare steel container and leave it wherever. In a hundred million years it'll be a nice lump of easily mined minerals, with lower chances of poisoning the local ponds.
But if you wanted to finely grind DRM proponents, I shall start carving out the millstones.
Only code that uses APIs that have been dropped is complicated to move. Complicated in a corporate sense, I urge to add: release and change management, specifically. I've updated a few code bases over the years, changes required have been minimal. Changes prompted by IDEs and static code analysis tools, plentiful - but those are suggestions. Often good ones, yes, but not necessary. Avoiding a 3 million bill, on the other hand...
That's not a good argument. As you note, basic protocol needs to know the IP address of the request originator (for the purpose of returning a response, if nothing else), so, forbidding the sharing of that information without consent wouldn't allow for anything to be served, including the page that asks for consent.
Tracking IP addresses requires consent; that's not the same thing discussed here, and it requires storage of the data.
A company can *say* they don't store it, but words are cheap and lies can cause expensive lawsuits. That's why there are certifications and audits and that sort of stuff. Not perfect, but that's all we have.
Seconded. I helped format a computer in 2002 with windows nt, both a few years old by then. Reason was it held an ISA interface card for a hydraulic press sensor of some description. Value of the computer, about fifty euros, value of the attached machinery about one hundred thousands, replacing the isa with pci or usb probably 10 grand. So nt and hopes of the psu not burning out it was. Still is, for all I know.
> some do some do not
And we know from other statistics that those who can afford to do the work for free often are the ones already privileged with higher salaries, better job security, etc etc.
I say that as one smack bang in the middle of the classical western privileged class, and maintains a few (tiny) open source projects. We lose the contributions of a lot of smart people who are too busy making rent because the industry is skewed against their gender, skin color, religion, etc. It's not a problem created by open source but it endures the consequences regardless.
Hitting the escape key let you in, but in our uni lab it meant you didn't get internet access, only intranet.
Blank password on those machines, meaning pressing enter meant you were in agd good, pressing esc not so much. Fellow student had to be told loudly, thought.
"It doesn't work!", he pipes up.
"Press enter", I say.
"But it works if I press Escape!", he counters.
"Then what are you complaining about, Sherlock?", or words to that effect.
I wasn't the sharpest tool in the box but he made me look amazing.
Good question and wrong example. The max failure was due to changing some important things without changing many other important things, not least of which being 'pilots need retraining' and 'poorly tested software attempting to cover for massive hardware changes, some of which made the plane impossible to handle' /he says, simplifying things quite a bit.
Whereas here the change isn't that far reaching and the nature of the beast hasn't mutated. DLL Hell, dependency hell, wasted space or slow start are the worst case scenarios, and, well, they're all problems that exist in the current state of things, at compile time or runtime.
So, optimism is allowable.