>The result is that European hi-tech entrepreneurs create their businesses in a friendlier environment, which is usually the USA.
The inverse of that is that this creates a huge market in the EU, where you don't have to be the best in class and the most capitalistic - you can be good enough and still make a good buck serving local clients.
I've implemented timers that had timeouts using unix timestamps, but only for multiplayer - when a player's attempt to connect to the server times out, etc.
Inside the game loop, we would keep the global tick counter that incremented on every tick, and timeouts would be based on that rather than on UTC.
The tick counter was updated only when the game logic was actually running. Our approach to pausing was to not run the functions that handled frame updates or physics updates, and to only run the rendering functions.
Generally we would never care about actual world time other than for some timeouts like for network (as the time passes for everyone), or for easter eggs like changing the tree models for Christmas or so.
I don't think anyone serious would implement event timers based on real time.
>I can assure you from having flown around a lot, if you are wildly outnumbered 3 SU-27 (err, F15) to your 1 F-18 you do not attempt a radar lock you do an IR only attack. The article mentions getting a radar lock first but that is unnecessary for IR guided weapons and in a 3-1 situation will just get you shot down.
Slaving heatseekers to radar is the standard way of employing them. I reckon by "having flown around" you're referring to DCS, which is absolutely unrealistic when it comes to engagements.
>Clearly any passive IR detector thats theorized to exist for years either doesn't exist or doesn't work very well. In theory, a smart enough IR camera should be able to notice something very warm indeed is getting rapidly brighter as it approaches you. In practice, these don't exist, or don't work. "Oh yeah they didn't have those when I was in, but they totally have them now" for the last 30 years. Apparently, not yet in 2026.
MAWS exist and they're employed on a lot of aircraft. I don't believe Strike Eagles have them though. An F-35 would get a missile warning for a heatseeker, it's not science fiction technology for quite a while now.
>I find it unfortunate that people who do this for a living can't legally comment, people who do this for a hobby are not asked or actively ignored despite extensive practical experience, and people who mostly have a grift of looking authoritative for legacy media get automatic blind belief despite sometimes spouting total nonsense.
You don't get practical experience by playing flight simulators, it's not comparable to how planes are employed as weapons systems.
It certainly feels like we are being squeezed from all sides. I think the push to require ID verification for websites is also part of the plot - it all feels too coordinated, like governments all over the world have the same exact agenda to destroy our privacy. At some point you will have to verify your ID to use any computer system, and it will act just as a terminal to the cloud.
I guess we will get the future that was seen in Sun Microsystems with their Ray thin clients after all, but in a way that will provide complete control over population rather than mobility.
What is in cards for us is complete slavery to digital systems.
Depends on the local laws. Where I live, they can either deal with it, or provide a secured storage space for the duration of the visit.
Either way, if a corporation wants their employees to use a device, they are obliged to make one available. Surrendering your private equipment to their management makes it not yours anymore.
>Many corporations require personal devices be managed to support remote wiping.
Corporations cannot require you to have your personal devices be managed by them. If you're surrendering your own gear to a company, it stops being your own device.
This is besides the point. The lead dev started going on a rant when facing a comment as simple as "this is informative, and unfortunate" on a video that he didn't like, and is unable to parse that statement as anything else but a personal attack at him. He threatened banning Louis over that unless he completely gave in. You can see the whole discussion in the video linked in the post above.
It's a communication issue at the core, and always doubling down is not making it any better.
It portrays the whole project as being unreliable.
He didn't step away. He made a post where he "stepped down" as the project lead and instead got replaced by a "GrapheneOS Foundation director", of which there are 3 including him.
That post has been deleted.
As far as I can tell, nothing has changed other than obscuring the leadership of the project a tiny bit. strcat is still active here in the comments.
Damn, if only we had some form of technology that would let a user allow or reject access to system APIs. Sadly this is impossible and cannot be implemented.
The solution is to use image-builder and bake your config into the image.