|
According to Evans Data's recently released Developer Population and Demographics Study, of the 19 million software developers in the world, 8.7 million are now writing apps targeted for mobile devices. Do you think that maybe many of them are doing some other development in addition to mobile?
|
|
|
|
|
Socket.IO lets clients and servers exchange events with any type of data structure. This helps enable chat rooms, realtime analytics platforms, and multi-user document collaboration apps. Realtime. Web. Web. Realtime. Sorry, I don't see a connection
|
|
|
|
|
On the heels of our recent foray into predictions, where we forecasted which contestants were most likely to get voted off or win The Voice, Dancing With the Stars, and American Idol, we are taking the experiment a step further applying it to the World Cup. Starting today, if you search for “World Cup”, “Predictions”, or any matches (both preliminary as well as later in the single elimination rounds) we will display the chances of each respective team to win. Chance of England win: 0 results found
|
|
|
|
|
Not available in my country 
|
|
|
|
|
Web applications may one day surpass desktop applications in function and usability—if developers have more programming languages to choose from, according to a Google engineer. Wait five minutes
|
|
|
|
|
"COBOL ought to be enough for anyone." -- Adm Grace Hopper
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
I assume COBOL on Wheelchair[^] is your web framework of choice. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
The engineer is wrong. We've already got enough server side languages to scratch anyone's preferences no matter how bizarre; and on the client side as long as everything still compiles down to html/css/javascript it's impossible for the situation to get any better.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Quote: You should have more choices of viable languages
That's almost right - I do not know of any "viable" language for web programming, all are bad.
|
|
|
|
|
If Hewlett-Packard (HPQ) founders Bill Hewlett and Dave Packard are spinning in their graves, they may be due for a break. Their namesake company is cooking up some awfully ambitious industrial-strength computing technology that, if and when it’s released, could replace a data center’s worth of equipment with a single refrigerator-size machine. Call me when there's a price tag
|
|
|
|
|
Yeah, when the measurements are "a data center's worth" and "refrigerator-size" it's time to move on.
|
|
|
|
|
Computer rack (a refrigerator-sized machine) filled data-center room will be replaced by a refrigerator-sized machine filled room with much higher performance. I think it's usually called an upgrade. 
|
|
|
|
|
Having read the article, what it is is HP's R&D doubling down on memristors; if they fulfill their promise of creating SSD non-volatile sized storage with DRAM speed, a dozens or hundreds to one condensation of IO bound servers is plausible. I suspect most applications would end up on the lower end of the range; the memristers might be 100x faster, but that much speedup would end up making lots of tasks that were IO bound become bottle necked on something else (compute, network, etc).
Edit: For reference, early SSDs were maybe 10x faster than HDDs in random IO (~2x as fast in sequential IO); and often generated 2-4:1 server count reductions for IO bound servers in data centers. Potential rackspace savings were often larger, since many of the servers targeted in early switchovers had very large disk arrays to boost IO parallelism (not capacity) as much as possible allowing a single SSD to replace 5 or 10 HDDs (the hdds only had tiny partitions to minimize seek time, leaving most of the drive empty). In practice, like with virtualization, they were often less as increased power density meant that the racks couldn't be fully packed without facility upgrades.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
modified 11-Jun-14 17:07pm.
|
|
|
|
|
"One meeelyun dollars."
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
Decima Technologies bought a few early prototypes to run Samaritan...
|
|
|
|
|
Figures from the Linux Foundation suggest skills shortages across disciplines and throughout Europe. Your latest in "Company funds study showing company's product loved"
|
|
|
|
|
ZDNet wrote: Seven out of 10 Europe-based Linux professionals have received calls where they were pitched new positions in the past six months, and a third said they had received more calls than in the previous six months.
Well, there is the problem. There is only 10 Linux professionals in all of Europe.
|
|
|
|
|
Following broad security scares like that caused by the Heartbleed bug, it can be frustratingly difficult to find out if a site you use often still has gaping flaws. But a little known community of software developers is trying to change that, by creating a searchable, public index of websites with known security issues. I'm sure nothing bad will come of this
|
|
|
|
|
Here's a list with all houses that don't have a decent lock..
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Google announced a suite of tools this morning for business owners, offering them a one-stop shop to update their business information, add photos, read and reviews and, of course, use Google+. Be a shame if no one could find your business, eh squire?
|
|
|
|
|
The new programming language is not faring well in some benchmarks compared to Objective-C, but Swift's easier syntax still gets a thumbs-up. There are four kinds of lies: Lies, damned lies, statistics, and benchmark tests.
|
|
|
|
|
Quote: Without leveraging optimizations in Apple's Xcode tool set, Splasm found that Swift was between six and 40 times slower than Objective-C, Splasm official Keith Gugliotto said. "
...
Even after turning on the optimizations, Splasm found that Swift ran 10 to 20 percent slower than the original test numbers in some cases and 10 to 20 percent faster in other cases. But Swift was still slower than Objective-C.
0) Benchmarks without the compiler optimizations turned on are worthless. The only value this have is as clickbait. Oh wait...
1) Do "original test numbers" refer to the objective C benchmarks or the un-optimized swift benchmarks? That's a huge difference in performance between the two but the article doesn't tell you which or give an easy way to find out because...
2) It breaks the cardinal rule of web news by talking about splasm's benchmarks but not linking to them.
Splasm's benchmarks[^] are Googleable though. Enabling optimization to both builds resulted in order of magnitude shifts in relative performance; but the closest swift ever came to obj-C was 6.4x slower.
With Android using Java that's only ~2x slower than native code in typical cases, unless Apple can make some really big optimization gains to the toolchain their newest and shinyest has performance poor enough that they risk the internet snark gallery abusing iOS apps as being slow and laggy compared to the competition in the future. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
If it doesn’t benefit the user it should not be done. This can be a new feature, a better user interface, a clearer wording, better performance, robustness, … Not all improvements have immediate value but they must have a value at some time. Coders of the world, unite!
|
|
|
|
|
Hmm, spending a day refactoring code doesn't benefit the user, but it sure as hell benefits the developer, sometimes halfing their Gin intake, isn't that important?
|
|
|
|
|
Halfing Gin intake is a good thing?
I say, "NO" good sir!
TTFN - Kent
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
