Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Firefox dropping support for older hardware. (Score 2, Informative) 134

Yes, Tell that to us. Just a couple weeks ago I had to search in more than 50 computer shops and stores and fail to find a computer capable of running DOS and latest version of general-electric PLC programming software that they still claim support for. because no one in here has anything older than 3 intel tics.
Yes, Please do blame us 3rd world countries for holding you back.
Am from Iran, 3rd world and all the import/export drama.

Comment Re:use-after-free bugs in Microsoft Edge (Score 1) 83

My point was, If you're working on something like Edge you should know a lot more than a developer that smashes a couple wizard forms together and some of the Edge guys probably did not, Just listed some of the usual things that go wrong to show how deep you have to think sometimes.
Has nothing to do with me being good or bad or bragging about it. I don't even own a single device with any microsoft products on it, so I don't really care.

Comment Re:use-after-free bugs in Microsoft Edge (Score 4, Informative) 83

In a single AppDomain with one single thread and no lazy references, sure. If you write anything complex it can go straight to hell if you don't know exactly what you're doing.
This includes every little messy detail on the multi-threaded multi-domain marking garbage collector with 3 lists and 5 heaps that traverses stacks of all threads on each collect, type inheritance with type casting direction, native calls with auto marshaling between managed and native types, AppDomains that should read eachothers' memory but not write it, etc.
Source: C# developer since 2k3

Comment Re:Oh please (Score 1) 89

They have a lot of servers and it's more cost effective to come up with their own solution for management, monitoring, maintanance, etc?
You can't exactly wait for a kernel patch or a fix for a breaking change if you're working with over a million servers.
Also to get bang for your buck You need your programs with a lot of patches to make them fit for your specific requirements and stripped of any code that goes unused or is deemed a security risk which means a whole lot of packages that are compiled in-house. hell even individual packages that are forked are posing problems for them (see https://boringssl.googlesource...)
All of this means you have to use your own package repositories which means even if they use redhat as a base it's not redhat anymore.
Did I mention ridiculous pricing?

Slashdot Top Deals

Every young man should have a hobby: learning how to handle money is the best one. -- Jack Hurley