934 karma · joined November 25, 2008
- Cardinal Richelieu
This was going through my head when I recently deleted 15 years of Facebook data. I am not the same person I was when I was 18.
I would argue in the same way that buying an expensive pair of boots that last longer than a cheap pair to be good value.
> You should have a look at Windows' desktop market share and get back to us. They still own the space.
What is the trend line and how much is that space growing by relative to other devices like mobile phones and tablets?
1) Most (if not all) FPSs at the time (Quake 3, Halflife etc.) had respawn times of around 10s after death. Counter-Strike introduced the idea of rounds which only ended when your whole team died. Scenarios would often play out with 8 players dead watching 2 players camping out the round.
2) IIRC, the default round timer was 5 minutes. This promoted conservative game play which slowed the pace of the game, especially for new players. I stopped playing CS for years but when I came to CS:GO, it was so refreshing that the round timer had been reduced to 3 mins. I spent countless hours being dead watching other people play out rounds.
Hence why they were run against MySql on CI.
We used SQLAlchemy on a Python project which allowed us to use an in-memory SQLite DB in our integration tests. This gave us blazingly fast database tests during development where a database was torn down and recreated, with data, for each test in milliseconds. When the commits were pushed, CI would run the tests against SQLite and MySql.
It worked extremely well and would be a tremendous amount of effort to handwrite SQL for both DBs. I'd do it on ever project if I could.
Versioned, offsite backups. For instance, if you have a database in an AWS account:
* Give the backup process write only (I.e. no delete permissions) to a GCP account.
* Create the backup in AWS and timestamp it
* Copy the backup to GCP using the above permissions.
* If you want to be more secure, copy the backup to a USBHDD (daily/weekly) and unplug it.
I think that's a surface-level interpretation of the benefit to Microsoft. Azure and GitHub CI are a great match for using idle server compute for one and Codespaces is another.
Check the historical interest rates of the US/UK vs SA for why that exists.
Any South African currently living there is completely unsurprised by this latest news.
Buried amongst the comments was this from one of the creators:
> On the live environment we were told at the time we had Perl 5.6, and a few BBC approved perl modules. Nothing more! So that meant that catalyst a other solutions were out.
I guess this could have been a defensive security policy. I think CPAN has had relatively few supply chain attacks like npm, pypi, et al. But that's probably due to it's popularity.
AFAIK, that's what JRuby does but Java had (has?) a bigger community and is more platform independent. Microsoft was a different company back then and wasn't supported on Linux. Betting on IronRuby/IronPython meant you had to use Windows as your platform.
https://www.amnesty.org.uk/why-taking-government-court-mass-...
1. Release often
2. When a release goes badly (and they will) do some version of '5 whys' and fix the root cause.
3. Continue to release often
That step 2 is often missing and what usually happens is that no engineering time is committed to the solution. Instead they implement more process which costs nothing, doesn't solve the issue and slows development.
Tories have done well to court the people that show up at the polls with things like keeping the Triple-Lock pension guarantee[1].
Like the Democrats, Labour's demographics have started to shift more to the well-educated (though I suspect this will swing back massively, come the next election). This alienated their traditional working class base who care more about their own economic realities than whatever social crusade is the flavour of the week.
Young Labour went out of their way to paint pro-Brexiters as racists and bigots. The dirty secret is that even Corbyn has been a long time Euro-sceptic. Because of the in-fighting on the correct position, Labour didn't take a hard stance on Brexit until very close to the end, IIRC. At which point, anti-Brexit votes were being siphoned off by the Liberal Democrats, with pro-Brexit votes going to the Tories.
[1]: https://en.wikipedia.org/wiki/State_Pension_(United_Kingdom)...