|
Microsoft was ‘very worried’ it was years behind Google’s AI efforts. Fear is the Microsoft-killer. Fear is the little-death that brings investment in shady companies.
meh. That was better as an idea, in practice it ended up pretty lame.
|
|
|
|
|
Easy-to-use programming language that drove Apple, IBM, and Commodore PCs debuted in 1964. Only 5 more years until retirement
many would hope
|
|
|
|
|
LinkedIn launched its first three games. They are available to access on the web for PC and mobile users. Because nothing says 'job search' like 'word games'
Although now that I've put it that way, 'word games' does sound like some interviews I've had.
|
|
|
|
|
As it turns out, it's quite difficult to keep track of 27,000 objects flying around Earth orbit. It was all Dr. Smith's fault. We're doomed!
|
|
|
|
|
OpenSilver 2.2 debuted today with a focus on helping developers revive Visual Studio LightSwitch legacy applications. I wonder if there are five people on CP that have even heard of Visual Studio LightSwitch? Count off!
I remember asking the product manager (aka marketing) for that product, "So, you re-invented Access?". He didn't like me much after that.
|
|
|
|
|
Microsoft has confirmed that the April 2024 Windows security updates break VPN connections across client and server platforms. "Microsoft is ‘putting security above all else,’ vows CEO Satya Nadella"
I suspect that quote is going to be the gift that keeps on giving
|
|
|
|
|
145,152-core Cheyenne supercomputer was 20th most powerful in the world in 2016. It might not be able to play DOOM, but you can probably create doom with it
Good luck getting a graphics card for it though.
"With a peak performance of 5,340 teraflops (4,788 Linpack teraflops), this SGI ICE XA system was capable of performing over 3 billion calculations per second for every watt of energy consumed, making it three times more energy-efficient than its predecessor, Yellowstone. The system featured 4,032 dual-socket nodes, each with two 18-core, 2.3-GHz Intel Xeon E5-2697v4 processors, for a total of 145,152 CPU cores. It also included 313 terabytes of memory and 40 petabytes of storage. The entire system in operation consumed about 1.7 megawatts of power." <-- wuff!
|
|
|
|
|
As JFrog security researchers found, around 20% of the 15 million repositories hosted by Docker Hub contained malicious content, ranging from spam to dangerous malware and phishing sites. I'm so glad someone's making use of containers
|
|
|
|
|
I prefer out-of-the-box programming.
I was working for a company having contractual obligations to deliver updates and bug fixes for x years. Lots of young, eager developers where actively++ promoting containers as The way to preserve a complete environment for generating an old system version with old version tools (which has been shown to be essential for reproducing bit-identical versions of the product). I was responsible for establishing a container based environment.
Luckily, I would say, we had an OS update. It turned out that the new OS version would not support the old containers, and that was as "promised": There was no promise to support the container version that we had used for our container based build system. The new OS version didn't make much long time promises, either. The disclaimers were clear and unambiguous: We could rely on our containers being runnable on new OS versions only for a fraction of our contractual support period.
For the container trials, we had to restrict future support to CLI tools, which is rather limiting. In principle, we could have switched to X.11 based GUI tools. Our primary IDEs were not X.11 based, but provided a lot of debugging and testing functionality that couldn't easily be replaced with X.11 based IDEs.
So containers were ditched as the basis for long-time support. It was simpler to set aside an old, real, machine with the old OS and old tool set to be used for future customer support, allowing GUI tools to be used (albeit old versions without the newer bells & whistles).
Containers may be useful for backend servers. While it in theory is possible to make end user containerized applications (based on X.11): In theory there is no difference between theory and practice, but in practice there is.
Containers belong way back in the back room, where *nix resides. Not in the user application domain.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
Why implement the requirement that way, instead of just setting aside a virtual machine image that contains all of the build tools?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
That was the old solution, but it had serious problems with USB (essential for the test equipment).
Also, the VMs turned out to be huge, and we had created lots of them. The hope was that containers would create an environment restricted to the tools and their runtime requirements - presumably a lot less than than the full VM OS environment.
I believe they found a cure for the USB problems, and disk space was getting cheaper, so maybe they did resort to VMs after I left the company. Picking up a ten year old VM could cause more friction than just running an old container - well, that's what we thought, and it turned out to be wrong.
Maybe Linux can run any and every ten year old container. Maybe your favorite VM manager can run any and every ten year old VM image. So maybe reverting to the old VM solution was a wise solution. Yet, I would certainly want to see that 10 year old solution running with all the physical interfaces (USB was only one; we still were using RS232 COM-ports, and software mapping 4 COM-ports to a single D25 LPT-style port). I am not at all sure that the old VM solution really could solve all the issues we encountered when running containers.
Whether VMs were a good solution or not: The container solution was not a good one. And then I left the company, leaving them to choose their future path without my competence. Visiting them again and ask them to show how they rebuild a ten year old system might be an interesting exercise!
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
Researchers have successfully used NASA's James Webb Space Telescope to map the weather on the hot gas-giant exoplanet WASP-43 b. "Winds light to variable"
|
|
|
|
|
Who cares for a weather forecast that is 280 years out of date?
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
Meanwhile, back on Earth, we can be sat looking out at torrential rain whilst the BBC Weather app tells us there's "0% chance of precipitation" at our location. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
The BBC employs reporters. If one is looking for accuracy, one should consult the gentlemen of The Times. 
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
An operating system on top of a distributed database, DBOS is a tantalizing glimpse of something that may eventually turn out to be cool. Databases all the way down
|
|
|
|
|
I can see how this would work for file systems, but how would it handle process isolation, resource allocation, etc. in a performant manner?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Didn't Microsoft already give up on this idea for the release of Vista?
It was too resource intensive for the PCs of the time. Maybe it might work better now.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Arc on Windows also represents an important milestone in getting Apple’s Swift apps running on Microsoft’s OS. Good luck with that
|
|
|
|
|
Hate to say it, but they need to hire at least one of MS's icon designers.
|
|
|
|
|
You don't like the ... uh, flossing look? 
TTFN - Kent
|
|
|
|
|
|
Making its AI-powered assistant generally available for developers and businesses, AWS also unveils free courses and a new Amazon Q capability in preview. All the apps it creates can also fire poison darts
I couldn't decide which Q to go with, and stuck with the older one.
|
|
|
|
|
This language is designed to meet the evolving needs of API developers, architects, and managers in an environment where the delivery of consistently high-quality APIs and related experiences is becoming increasingly complex and critical. An API API
Because of course it's all about the model. No one EVER needs to have some processing logic.
|
|
|
|
|
Despite seemingly exiting Microsoft, Bill Gates still plays a major role in the firm's decision making process. You can take the Bill out of the executive office, but you can't make him give up the keys
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
