Re: Cross platform coding
Don't forget another big app rewrite from 7 to 8 which stamped on it again just to make sure it was really dead.
16866 publicly visible posts • joined 13 Jun 2009
You really need a heat sink stuck on top of the CPU, at least.
I'd think turning off link previews in messaging apps is one of the first things any self-respecting commentard would do to, firstly to stop malware from dodgy spam messages being downloaded, secondly to stop your phone number being confirmed, and thirdly to stop being geolocated from your IP address.
Both cases appear to have been a function of asking someone who doesn't understand statistics, to merge datasets from multiple sources.
Nope. Both cases are due to management decisions brought about by running IT on a shoe-string budget (another management decision).
Everything gets shoehorned into Office no matter whether it's appropriate or not.
The 2018 UK accessibility website law only applies to public sector bodies. The EU Web Accessibility Directive doesn't apply in the UK thanks to Brexit but if any company has a web presence which sells goods and services in the EU/EEA market then they will need to meet the same standards by 2025 anyway.
And as if by magic, mere minutes after the announcement, the button was pressed and the trailer was released.
There's also the culture and work ethic - look at the problems TSMC are having in Texas, where Americans won't work hard enough apparently, yet it's a fact Americans work longer and harder than Brits. Could you imagine how TSMC would cope with the likely workforce in say Grantham, Kilmarnock, or Warrington.
I would bet it's more down to not being able to find local people with the skills which, as the US is not a great chip manufacturer any more, is unsurprising. The solution as always is for employees who do have the skills to work longer.
So if they were to rock up in Grantham there is no amount of employee overtime that could get them out of that pickle.
I mean, who knows what "rogue code" is.
The only thing you can be sure is if the main system fails and the backup system fails in exactly the same way, it's not the because the chances are "like winning the EuroMillions" lottery, it's because the same software failing in exactly the same way on the exactly same input.
The survey was a surveillance propaganda exercise, the article was just a useful idiot in the wider privacy debate.
rounded window corners which is a huge productivity boost because you can visually tell wherre one window ends and another begins. This alone is enough to make it almost as good as windows 7
It's almost as if making everything flat slabs of indistinguishable colour was a mistake but it's still too early to go back to a 3D look with colour hints as they'd lose face so they found another way almost as good which was copying Apple.
For some reason it wasn't too easy find, I couldn't find the file but it was referenced in a commit. I also stumbled upon a reference in the same commit to the big brother of the cut-down Nano-X build in Elks:
Nano-X AKA Microwindows: Github, Website.
It's a windowing system for small devices with three different APIs based on Win32, X11, and Xlib.
Looks like this is the chap:
https://github.com/ghaerr/elks/tree/master/elkscmd/nano-X/demos
Usually the more documentation you have the better, but that's not true in JavaScript's case.
What the fuck major disaster could possibly occur which would require a national broadcast to EVERYTHING?
In case of in case of alien invasion, Will Smith would have got out of bed and kicked alien butt earlier if he had a phone with emergency alerts.
This appear to have got worse over the last decade, it actually makes me miss the Microsoft of old.
The guarantee started 2 years ago when someone first thought of it and will last until you try and get into contact with Google support who will say it's a hardware problem and re-direct you to HP and HP will say it's an OS problem and re-direct you to Google support.
Chromebook 128GB+2 in grey, Chromebook 128GB+3 in black.
I hope they don't use non-standard USB ports.
The problem with XUL and XULRunner was it was horrendously documented so nobody could write apps with it (I did try myself). If they had documented it better, they might have even done themselves a favour because apparently one of their reasons for dropping it is they didn't know how to maintain it any more.
The Australia Chrome-like theme in Firefox 29 annoyed users and was a driving force behind Pale Moon
That sentence was auto-incorrected... I remember reading a while back that Mozilla's UI mock-ups came before Chrome's UI change, but Mozilla took such a long time to execute that Chrome got there first with the same idea (either copied or independently), but don't ask me to find the source now.
Which is also Mozilla's problem today, they take such a long time to execute, probably due to lack of resources and having to dedicate the resources they do have to following Google's latest mad idea as it's the de facto standard. Other browser developers can make minimal changes to Chromium where most of the work is already done.
Zeros and Picos were less powerful, there's the CM versions, the 400 was a different form factor, and some updates to the earlier models were released with the same thing in a smaller size or sometimes with less memory or only added wifi or more GPIO pins.
The official power supply now delivers up to 27W even though Tom's Hardware could only make a Pi 5 use 7W when stressing it and changed the configuration so it drew 0.05W when in standby.
Over 16 reasons why Jira and Confluence suck
Jira is not as good as project management software for managing projects and not as good as bug tracking software for tracking bugs, it's just an event horizon of stupid user interface choices coupled with crazy backend design which makes it impossible to revert mistakes (and we do make mistakes because we're only human after all). Once a company realises their provider or end clients also use Jira then all bets are off, they connect up their Jira instances in the mistaken belief that it will make working with Jira easier and the fail grows exponentially as comments get sent externally that people didn't mean to send and workflows don't match up. The only thing that makes working with Jira easier is ripping it out and using better tools for the job.
Previously, I liked mobile Firefox on Android, but they yanked that out from underfoot and it's a shitty Chrome back end browser too now.
No, Firefox uses GeckoView instead of WebView or Blink.
Also, the extensions I was using with mobile Firefox are GONE (Can't do that Dave... not in this browser engine)
They're removing restrictions on Android extensions in December.