Exactly. Sony/Playstation can lose their right to issue further licenses, but the existing licenses should be honoured. As that's apparently not baked into the existing contracts, someone needs to legislate that such basic consumer rights are required, and all existing and prior contracts interpreted as if these rights were in place.
Make it work the same as delisted games where you can go into your purchase history and click download.
On desktop it keeps adding forced pauses to scrolling, of varying sizes, and you need to scroll down a between 1 and 10 pages worth to begin scrolling again.
It might "work" just fine on mobile (or not) but you may have stopped trying before reaching the point of re-scrolling, because it's insane.
I eventually managed to get far enough into the article that I thought I saw the main stat - the stat that 26% of the citations were hallucinated. Then the scroll threw me back to the top again and I gave up entirely on reading from my phone.
Coming back later on desktop, I see that the percentage keeps climbing the further you manage to make it down the page. The real stat is 60% of the citations were hallucinated.
I compile and run utilities on my Mac all the time, and I've never spent a penny on dev tools or unlocks.
Yes, there's a fee to get access to the App Store, but almost nobody on the Mac uses the App Store... the fee is mainly for putting stuff on iOS (and likely watchOS, tvOS).
The fee also gets you the absolute latest Xcode, but go back one version, and it's entirely free.
On Mac, you can install brew, and use it to install gcc, clang, qemu, whatever utilities you want.
You used to need the developer fee to put stuff on your iOS device at all, but these days you can put stuff on your personal devices without a fee, but the binary expires in a week... enough to learn and debug, but not ideal for a personal tool. That's about the only annoyance where the fee comes up... long term deployment to iOS.
> you can put stuff on your personal devices without a fee, but the binary expires in a week... enough to learn and debug, but not ideal for a personal tool
This sounds like dystopian cyberpunk written in the 80s
The Locked Tomb series:
- Gideon the Ninth
- Harrow the Ninth
- Nona the Ninth
Liked the first Locked Tomb, didn't really enjoy the remainder of the series.
The Witch King (from the Murderbot author), was alright.
The Time Travellers Almanac. Time Travellers Almanac was meh. A set of short stories, but many retreads of the same ideas we've seen over the decades. There was one good story, and one other interesting concept...
Road to Roswell and Crosstalk. Connie Willis' books were great, as usual.
Brzrkr. Keanu's book was meh.
The first five of the Kate Daniels Series:
- Magic Bites
- Magic Burns
- Magic Strikes
- Magic Bleeds
- Magic Slays
Kate Daniels is doing an acceptable job filling in for Dresen's absence, though book 3 and 4 go a bit heavy on the romance side.
Pre-orders pending on the next Murderbot book (Platform Decay), and Dresden (Twelve Months)
I'd argue that 68K is simpler to learn and use. You get a similar instruction set, but 32-bit registers, many of them. It's even got a relocatable stack so it can handle threading when you get to that point.
I agree, I feel like the 68k architecture was a dream for assembly programming. each register is large enough to store useful values, there are lots of them, there are instructions for multiply and divide. This allows you to focus on the essence of what you want to accomplish, and not have to get side-tracked into how to represent the X-coordinate of some object because it's just over 8 bits wide, or how to multiply to integers. Both of these seemingly trivial things already require thought on the 6502.
Pinch zoom is the preferred method, it just needs to zoom at a usable (much faster) pace.
I have no idea what input events zooming generates. Perhaps an option in the URL could be used to turn on a log of input events that people can copy/paste and submit back to you, so you can get a sense of what events are coming from various devices and input methods without having to find devices to try them all yourself.
Plenty of map sites have spent years broken on Macs, not handling smooth pinch-zoom or Magic Mouse smooth scroll wheel events. A slight 3mm movement of a finger going from fully zoomed in street view to fully zoomed out planet view. I'm assuming every micro-movement event is treated as a Windows scroll wheel event where you expect to move a decent chunk on each event.
However you're treating zoom inputs, you've got the opposite effect. A full zoom motion barely does anything.
Perhaps someone at Microsoft threatened physical harm to a Google engineer if they didn't remove the videos... and they caved into their demands rather than reporting the threat, or perhaps did both.
Typically "Cost Of Living" increases target roughly inflation. They don't really keep up though, due to taxes.
If you've got a decent tech job in Canada your marginal tax rate will be near 50%. Any new income is taxed at that rate, so that 3% COL raise, is really a 1.5% raise in your purchasing power, which typically makes you worse off.
Until you're at a very comfortable salary, you're better off job hopping to boost your salary. I'm pretty sure all the financial people are well aware they're eroding their employees salaries over time, and are hoping you are not aware.
Tax brackets also shift through time, though less frequently. So if you only get COL increases for 20 years you’re going to be reasonably close to the same after tax income barring significant changes to the tax code.
> 4. M1 has over 600 reorder buffer registers… it’s significantly larger than competitors.
And? Are you saying neither Intel nor AMD engineers were able to determine that this was a bottleneck worth chasing? The point was, anybody could add more cache, rename, reorder or whatever buffers they wanted to... it's not Apple secret-sauce.
If all the competition knew they were leaving all this performance/efficiency on the table despite there being a relatively simple fix, that's on them. They got overtaken by a competitor with a better offering.
If all the competition didn't realize they were leaving all this performance/efficiency on the table despite there being a relatively simple fix, that's also on them. They got overtaken by a competitor with better offering AND more effective engineers.
