Did you ever try a bike from a bike shop? This sounds like a department store bike experience. Multispeed bicycles are not generic widgets you unbox, hop on, and go. They need tuning, like a musical instrument, and a lot of the adjustments are interdependent on one another.
That's like saying you can't just buy a harbor freight engine and expect the carb to be properly tuned. 99% of people are going to have no problem with how it performs as configured right out of the box.
> The average department-store bicycle is ridden about 75 miles in its lifespan from showroom floor to landfill. The manufacturers know this, and build them accordingly. Department-store bicycles are most commonly sold in a partially disassembled and un-adjusted condition.
I should also clarify that SINGLE SPEED pedal brake bicycles ARE nearly maintenance free, and those DO work for most people out of the box in whatever state it might be in.
If you want to try (and I would recommend trying, since even this early version of the program is an amazing design, with much to learn from), please be aware of the following:
1) The source code is incomplete; you will need the original EA IFF 1986 (March) files to fill in the gaps. You will also need to find a replacement for the LFMULT() function.
2) The paths to the header files will need editing.
3) The original program was built using the Lattice 'C' compiler, and it uses a couple of library functions which are specific to that compiler, such as stscmp(), stcu_d(), setmem() and movmem() for which you will need to provide replacements.
4) You may want to replace the BootIT() function with a stub, which originally seems to have been part of the disk copy protection scheme.
This should get you started. Once you get the program running, watch out how you use it:
As was common in these days, string buffers are rather short (e.g. 20 characters for a file or drawer name, 30 characters for font names) and the code is oblivious to this limitation, easily leading to buffer overflows and crashes.
Also, the hardware acceleration which Deluxe Paint uses is not properly secured by calling OwnBlit()/WaitBlit()/DisownBlit() in the proper sequence at all times (some are correct, some are not, and the code shows that the developers struggled with mitigating the ugly side-effects of not getting it right). This will cause the image processing functions to glitch and corrupt memory. Apparently, this happened only rarely in 1986 because the Amiga system was "slow enough" so that writing to the Blitter registers while it was still running didn't always lead to things going awry.
> Posts that assume everyone considers certain changes to Firefox "anti-features" aren't going to win everyone over, either.
This seems like a bad faith characterisation. The discussion was about ars's activities, and I think it is reasonable to assume silversconfused was guessing at ars's opinions on these changes, not at "everyone's" opinions.
An EV drivetrain is extremely simple and reliable. They are dragging their feet on purpose to extend their returns on ICE investment, not because it's "too hard".
"An EV drivetrain is extremely simple and reliable"
I don't know why it is so popular to repeat this over and over because it seems palpably ridiculous to me.
Everybody has plenty of experience with electrically powered appliances, and many if not most of them only last a few years. I'm not suggesting this is inherent, just that there is no reason to consider them simpler or necessarily more reliable.
If there were washing machines or smartphones that you could expect to last decades, then I would find the idea of EVs being super reliable more plausible.
They think in terms of platforms, their next gen platform has all kinds of other requirements (think >100 processors, sensors etc.). The good news is that their next gen platform will be electric and that they hiring >5000 new software engineers to build out the user experience.
Unless EV door handles and airbags are that much more complicated, I must be missing something. The problems with EVs are support infrastructure and profitability, NOT reliability and complexity.
There's no reason for local software to stop working when a remote server is unavailable, reconfigured, neglected, or your clock is wrong. They are doomed if they think this is sustainable.
It was a time bomb to disable functionality after a certain date and should never have been there in the first place. The decision to silently disable the override in about:config is just more evidence of how sick this it. This is not software empowering the user. This is software assuming the user is a moron who may break it.
We have all the proof we need that MS is running an ad farm from the base windows experience. What proof do you have that he was infected with malware beyond that?
Where's that proof? I also run windows 10 at home, no issues with cpu or ads. The build servers at work? Same. no IE cpu hogs, no ad farms ... That's why i think this is some malware that has gotten by, and not ad farm.
That's just making the user need _more_ passwords, and will result in bad password mangement and lost access. Also pins are quite a bit easier to shoulder surf, so this is just nuts.
If they are going to pay for 1/10 a developer, is anything stopping you from picking up 10 of these orgs as employers at the same time and delivering 1/10 of your effort to each?
I think andrew_19’s comment about the guy who subcontracted the jobs out to people where 1/10 salary is thought to be hitting the jackpot is probably the better way to go here if you’re even seriously considering the job in the first place. The main problem there is making sure your contract explicitly allows or at least doesn’t prohibit you from farming the work out.
The switching costs alone would eat half your day, and of course they're hoping to get much more than 1/10th of a developer despite only paying for 1/10th of one.
So if you're a 10X developer, and switching jobs will eat up half your time... you could take 5 jobs and provide 1 developer's worth of skill to each, right?
Non competes only matter if they're competing. At the price they are offering I'd spend about 1/2 an hour trolling stack overflow for random bits of code, push whatever I find whether it is relevant or not and call it a day. This kind of blind abuse is literally to encourage H1B abuse. They are just going to use this to claim they couldn't find a local resource and export the job. It's illegal and should be cracked down on harder than a fleck of marijuana in Texas. It's apparently a felony to have weed in Texas, why is it not a felony to commit employment fraud/H1b fraud? You're destroying lives other than your own in one case and just enjoying yourself in another.
It's hard to make parts for things that are designed to be unrepairable.
That said it's also hella not cost effective. I'm in $400 or more, and have only printed a few daily use items. My printed clothes dryer knob has been working great for a few years, and my printed curtain rod brackets are working fine so far this summer. The replacement button I made for my father's CNC lathe is working fine a few years in too. That said, being able to sketch something, bang it out in openscad, and have a part waiting for me on the bed the next morning is pretty magical.
