The iOS simulator compiles the code for the host platform with the iOS APIs. It has never emulated the target device.
1586 posts • joined 8 Jul 2009
I can't comment on newer Xbox consoles, but you pretty much had full control over the original Xbox. You could even show a static image while you rebooted the machine (which took a fraction of a second) - I know of at least one game that did that after each level. (Not my responsibility, but it was a game I worked on.)
On the Xbox360 DirectX was a super thin layer on top of the hardware (the API wasn't even implemented as proper COM interfaces), and the OS was basically a cut down XP kernel which ran on a single hardware thread on a single CPU core. The compiler didn't even support C++ exceptions properly - they were that focused on performance (support was buggy from when we first got our hands on alpha hardware (basically beefed up Apple Power Macs) and we were told that it would never be fixed).
I'd be very surprised if they'd changed those things. (Well, I guess the compiler is better these days now there are x86 processors under the hood.)
Their financials can be found here: https://www.sec.gov/Archives/edgar/data/1764925/000162828019007428/slacks-1a3.htm
Maybe, just maybe if Slack was actually a decent piece of software it would do better.
But it isn't, probably never will be, and so won't.
Slack is mediocre at messaging, and absolutely shit at video conferencing. I think the only reason people in larger companies use it is because it's marginally better at messaging than Teams (but light years behind in video).
The feature I love the most about the Slack app is when it tells you a message is too long and if you want to view the whole thing you have to open it in a web browser. Pure class.
Apparently (I've just discovered) the Plus Pack for Windows 98 was the first public release of "Compressed Folders", but I honestly don't recall it being useful or even usable - if it had been I wouldn't have kept needing to use other tools to open ZIP files.
I tried to avoid Windows XP as much as possible (at least on my home PCs) and jumped straight from Windows 2000 to Windows 7, so maybe I just missed out on that particular feature.
It is entirely possible, of course, that my memory is even more shot to shit than I... err, remember. :)
RISC-OS also had support for pluggable file systems.
I remember when the first ZIP files started appearing most other machines needed some third party utility to read and write to them (most still do). Someone kindly (bravely) wrote a RISC-OS file system driver for them so the whole OS and any application that needed to access their contents could do so as if they were a regular drive.
Fast forward 30 *years* and Windows Explorer has finally got "native" support for reading/writing ZIP files. (But no other compressed formats.) The lack of innovation in our industry is all rather depressing at times. There are still many cool features of early systems that are missing from today's "advanced" operating systems.
Back in the mid 90s I was working for a small games company. Being a semi-senior member of a small team I was often the person others turned to with questions. Most of the time I was happy to help, but occasionally I just needed to get stuff done. One particular day I had to get a demo finished for the following morning, and the interruptions were coming thick and fast. I ended up taping a big “Fuck off, I’m busy” sign to the back of my chair. Which worked really well until about half six in the evening when I got a friendly tap on my shoulder. “That’s not very nice,” said the cleaner with a big grin on her face.
My typical work day consists of typing furiously and mild mouse waving for five minutes, followed by 110% CPU usage while the compiler does its thing, followed by five to 10 minutes of heavy 3D rendering while I test.
I'm lucky to get two hours out of my current work-issued laptop. I reckon this might stretch to three hours - if I'm lucky.
I guess the point of measuring speeds that people actually have is that it includes some nod to economic factors with regards to connections. Everyone with a fibre connection could get a 1Gb+ contract, but if the costs involved are prohibitively high, not many people will actually do it.
A progressive tax is one where the tax rate increases as the taxable amount increases. So what I was suggesting was zero tax on any revenue under half a billion <currency_unit>s and progressively more on revenue over that value up to some maximum revenue value at a top tax rate.
And I think it's fair to say that just taxing profit clearly isn't working after a certain point. There are too many loopholes and ways to avoid it. Which is what started this conversation in the first place.
A progressive tax on revenue should be levied in an ideal world. But the bottom rate shouldn't start at the first <currency_unit> earned.
Without thinking too much about it, a 0.1% rate on revenue over 500 million would be a good starting point, rising to 10% on revenues over 10 billion. That would hit the largest companies the most while leaving small to medium businesses largely unaffected.
A severe restriction on the amount of money that can be transferred to a sister company for "licensing" wouldn't be a bad thing either. (Either that or make that taxable somehow.)
Good luck ever getting any of that passed into law though.
There has to be reasons.
Given that as recently as the year 2000 half a billion people in India didn't have electricity in their homes (every village now has electricity since 2018) and even today around 12% still don't have access to a basic water supply I don't think video games are particularly high up on most people's list of concerns.
I never understood the logic of firing someone who makes a mistake. If they repeatedly make the same mistake, sure, but all you're basically doing otherwise is replacing them with someone who hasn't learned not to make that mistake yet.
And if the rest of the company doesn't put procedures in place to mitigate that mistake from happening in the future then nobody has learned anything and you're back to square one.
The standard console in Windows 10 has supported Ctrl+C/Ctrl+V for copy and paste for quite a while now. It's even smart enough for Ctrl+C to copy (if there's a text selection) or kill the current process as you would expect. Suffice to say I miss it when I have to use bash for something (talk about awkward copy+paste functionality - enter to copy, right click to paste... uh-huh, that makes sense).
And you've always been able to change the font - at least as long as I can remember.
This is what happens when you have a bunch of mediocre developers and a popular web browser. *Everything* has to be jammed into the browser instead of being separate applications.
Why do mobile apps exist? Because mobile browsers and mobile versions of websites are so piss poor. So why aren't desktops treated the same way? If you can be bothered to make an app for one or both of the major mobile platforms, why can't you make one for the three major (one major and two minor really) desktop platforms out there?
Browsers need less functionality and fewer potential exploitable back doors. Not more.
As I understand it, Chrome sets the END_STREAM bit of the last HTTP/2 data packet to be sent. Other browsers send the last true data packet as normal followed by an empty packet with the END_STREAM flag set.
I guess the bug in Node.js is it throws away the data of any packet with END_STREAM set. (But I really am just guessing here.)
I think it would set a bad precedent to put a former president behind bars
It would be a bad precedent to put someone behind bars just for no longer being president. In this particular instance though, if Trump fails to get reelected we should throw him a massive street party.
And then throw him in jail for be a corrupt, insidious cunt of a human being.
I understand the reasoning behind reversing the operands, I just don't like it. It doesn't scan well in my head.
In any code base I touch these days (usually C++) the "assignment in conditional expression" warning is promoted to an error.
And just don't get me started on the if( type variable = expression; variable ) syntax of C++ these days. I'm feeling nauseous just thinking about it.
Nice idea. The problem is the GPU. It's not supported by Metal, which is basically the main requirement for newer versions of MacOS.
Not being able to use the latest OS is not really the thing I have a problem with. It's the fact Xcode is so tied to the OS that it's impossible to run it on older versions of MacOS. That's a shitty way to force people to upgrade. Especially given the version of the OS I do have installed is only three years old. Visual Studio 2019, on the other hand, still supports Windows 7, which was released 11 years ago.
The only reason I have to upgrade is Apple's bullshit planned obsolescence.
Older iMacs (like the 2011 one I have) are barred from running the latest versions of MacOS. And therefore I can't run the latest Xcode. Which means I can't release any iOS apps.
Yes, the machine still works - it's probably one of the most underused computers in the world. But it's completely and utterly useless to me now.
(I'm not upgrading anytime soon though. Fuck Apple.)
Using the horizontal blank interrupt to switch hardware sprites or otherwise modify GPU state was a common trick on a lot of old consoles.
In the case of sprites, the hardware would allow you to display x hardware sprites on screen per frame, which were usually controlled by a few registers that just needed to store the start address of the sprite data, its position on screen, and (optionally) its size. Once set up, moving those sprites was just a matter of updating their position registers.
However, it was soon realised that the "x sprites per frame" limitation could really be thought of as an "x sprites per scan line" limitation. By hooking into the horizontal interrupt (which was triggered as the monitor's electron beam was being repositioned at the start of the next scan line) you could update at least one full hardware sprite per line, and thus fool the hardware into rendering more sprites per frame than it claimed to support.
A single height enter key is just American standard. With a proper UK layout, that wouldn't be an issue.
Nor would the key-travel distance be a problem for me either. I prefer slimline keyboards over mechanical behemoths that require busloads of school children to jump up and down on a key for it to register a "tap".
The things I look for in a laptop keyboard are:
Proper UK key layout.
Power button away from the rest of the keys.
Right-Ctrl on the end of the row (and not jammed in the middle next to the space bar).
Decent cursor key cluster.
And things I would like (but rarely find):
Horizontal spaces between escape and function-keys, and function keys grouped into fours.
Vertical space between the function-keys and the main keyboard proper.
Biting the hand that feeds IT © 1998–2020