|
UC Berkeley’s SETI@home, one of the most significant citizen-science projects of the late 20th century, brought the search for intelligent life to PCs. It hasn’t yet found what it set out to, but there’s still hope. "If you don't answer I'll just ring it off the wall"
|
|
|
|
|
Yup.
This proves without a doubt what the Earthman's speciality is.
@home spyware, for spying on other Earthmen, obviously isn't enough; we've just got to take it interstellar.
Just wait until the Andromedan Union starts imposing fines.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Meanwhile, the Search for Terrestrial Intelligence also continues to draw a blank.
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
That's right; I'm just passing through.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Since I’ve been working with the community on porting desktop applications from .NET Framework to .NET Core, I’ve noticed that there are two camps of folks: some want a very simple and short list of instructions to get their apps ported to .NET Core while others prefer a more principled approach with more background information. Convert before they merge them all into one.NET
I mean, you've nothing better to do, right?
|
|
|
|
|
One .NET to rule them all!
... Until Thursday.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I still don't know what .Net Core is for, or how it's "better" than .Net Framework...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Main selling-point is that it's cross-platform and, I assume, somewhat cleaned up, so more performant. It will be .NET going forward.
It seems that new frameworks and libraries are now being built on that rather than traditional .NET.
E.g., the recently-released ML.NET is .NET Core based. As is Q#, so usable on Mac and Linux.
Kevin
|
|
|
|
|
I don't care about any of that.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Fair enough but you're not Microsoft's only customer.
Kevin
|
|
|
|
|
But I'm the only one that matters.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I concur. I'm the only M$ customer that matters
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
W3C hands over development of HTML and DOM standards to browser vendors (WHATWG). Standards? We don't need no farging standards (We've got Chrome)
|
|
|
|
|
0) Why would an entity that doesn't have skin in the game (W3C) be put in charge of a standard?
1) Does having new stewardship indicate that things will move faster, or will the "too many chefs" rule still plague/inhibit the ratification perocess?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
0) I'd say that (right or wrong) it grew out of the standard bodies being more academic and "pure". We still have the IETF as one example continuing this.
1) I'd suspect it would go faster. The 802.11 WG seem to be good for making decent progress, and "the new Microsoft" seems to be better at playing well with others than they have in the past. I do worry that Mozilla might act up just to be different though.
TTFN - Kent
|
|
|
|
|
Kent Sharkey wrote: 0) I'd say that (right or wrong) it grew out of the standard bodies being more academic and "pure". We still have the IETF as one example continuing this.
If I've learned one thing from my four separate (and seemingly endless) spells in university, it's this:
If something exists in the real world, don't let academics anywhere near it -- and if they get close, ignore every word they say.
The real world requires real solutions, not pie-in-the-sky cr@p that has no grounding in reality.
Them as can...
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I also would have gone with, "academics leading this gave us CSS". That alone should be grounds for exterminationgoing with a more practical standards body. 
TTFN - Kent
|
|
|
|
|
That lot will be first against the wall, Brother!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Things were so much better when it was just IE4 and NutScrape, and all you had to worry about was how they calculated table borders.
Remarkably (VERY remarkably!) we used to be able to view all web pages perfectly well, back then, and security was a doddle, when the average page didn't have 13,465 lines of code tucked away behind its fourteen lines of text and a checkbox.
Two things went wrong with the Interwebs:
0. It was supposed to be "for the people", but devs took over, and turned it into a nightmare.
1. "The people" decided that twatter and farcebooj were all they wanted, and turned it into a nightmare.
If the net had been done exactly as I want it, I'd have no room for complaint.
(Not that that would stop me complaining, but jes' sayin')
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: we used to be able to view all web pages perfectly well
I have a very, very different view of "back then".
"Back then" we used to have to bend ourselves backwards and tie ourselves into knots to ensure that our sites worked on IE and Mozilla and Safari and then Opera and then Chrome. And then IE evolved and we had standards and quirks mode. And different rendering modes. The box model was the least of our problems, and what you ended up with was hacks on hacks on hacks. And lots of tables.
It was horrible and a massive time suck.
To the general web users, however, "things worked". Because we worked so frickin' hard to make it work.
cheers
Chris Maunder
|
|
|
|
|
A token gesture acknowledging their redundancy. Good.
Standards should have been set before they were implemented. Or, at the very least, before they'd been implemented so long ago that every modern browser manufacturer had implemented them and every web developer used new features as par for the course and everyone was already onto v.Next.
The W3C didn't have to come up with the plans. They didn't have to exhaustively test them (500M websites were well on the way to already doing that). They just had to act as a central repository for the standards, and if they rev'd those standards monthly then it still would have been better than being years behind.
And yet even with all of this they were entirely ornamental because there were no consequences to not following the published standards. Quite the opposite: there were consequences to sticking to the standards and that consequence was losing market share to other browsers that made life nicer.
cheers
Chris Maunder
|
|
|
|
|
Microsoft and its PC partners may be ready to take the wraps off a new Windows 10 Home edition that potentially would work on more powerful PCs than those which ship with reguar Windows 10 Home. "In a super jet he comes from a billion miles away, from a distant planet land"
|
|
|
|
|
One Windows!
Roolz, ya?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
That means that when a new website is registered it will be crawled by Google’s smartphone Googlebot, and its mobile-friendly content will be used to index its pages, as well as to understand the site’s structured data and to show snippets from the site in Google’s search results, when relevant. It's a small world, after all...
|
|
|
|
|
I don't see this as a problem.
winio pretends extremely well that it's a mobile OS, so it should fool them into indexing it a lot quicker than other OSes that are far more suitable than winio for desktops and laptops -- like iOS, androud, and Symbian.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
