This is a crazy leftist plan that will result in either hosting complete cultural rubbish to match the quota, or artificially limiting the catalog to match a quota. For god's sake, end this totalitarian EU before its too late.
Took a look at Julia. Seems like a really nice language. BUT... every time I see a new language I can't help but think every new language is doomed to reinvent Lisp, but badly. Other than the typical hatred of prefix notation, what does Julia hope to give me over Lisp or Scheme?
If you're going to deliberately obscure your code, then there is no hope for you anyway. I can see lots of specialist applications where allowing unicode could really help readability. Would I advocate using it? Probably not. But I think it should be allowed.
In terms of tight math loops, you're right C is hard to optimise. However if you want to write an OS kernel, what else are you going to use? Those details you specify in C suddenly seem necessary to keep tight control. We don't for example want our OS kernel doing garbage collection. Or at least I don't think we do.
C++'s ambiguity between >> as bit shift and templates is a known defect in the language. As for newlines, I don't see that issue as significant as spaces, being whitespace. Every editor in the world knows how to look at a newline. Not so for tabs and spaces.
They could put their ads in the streams or put requirements about the developers putting their ads in by specification. But they don't. I don't know what they're on about, but if the 3rd party apps become unusable, I won't bother with Twitter anymore. It's not like they even have a Mac app, and their apps on other platforms are marginal in quality.
Knowing how computers work I would have zero sympathy for a computer begging for its "life". However, I would be amused enough to hear it out to find out how clever the programmer was.
I don't know what Amazon is replacing it with, but I'm surprised that SQL databases got so big and stayed so big for so long. There are nice things about them, there is no doubt. But there are so many horrible things about them. Why hasn't Oracle moved with the times? Why haven't they researched and created something better after all this time with all that money?
Depends what kind of user you are. For simpleton users, there is no lock-in. For me, I have quite a bit of lock in because I rely on quite a few important apps. I'm also locked in by iTunes, Macs, iPads, AirPods, AppleTV and other things. Sure I could move, but the number of comfortable things I'd have to replace is painful to think about once I start thinking about all of it.
I hope Apple isn't going to a vertical keyboard. This would be incredibly stupid for a number of reasons. One being that video watching is a major use (maybe even THE use case), and vertical would suck.
The excuse given for iPhone 7 that the case isn't big enough for headphones doesn't wash either. Apple's minimalism is going too far, and I'm not sure how much more I can stomach.
This is all fear mongering. There are reefs in the world with water FAR hotter than the great barrier reef. Despite what researchers who benefit from government funding would like you to believe, there is far from agreement that the reef is in any way in trouble.
This is a metaphor for the endless war between progressives and conservatives. Progressives think they know better and want to "do good" and change the world. Conservatives think that systems are complex and your efforts to mess with them will have unintended consequences.
It is a flaw. Unix makes files and text the user API to the system, and these things are inherently untyped, unchecked and unsafe as APIs. Nobody would design a serious programming language or API like that.
Now you may say, yes but it's quick and easy. It is, but it's possible to make a system both quick and easy as well as unfragile. Lisp machines come to mind as an example.
Oh I don't know, it's pretty bad. It doesn't solve any of the things that inevitably come up, like what happens when you change your classes, how do you migrate the legacy data? It's not bad if you're a school student hacking some rubbish. But in the real world it's pretty useless.
Efficiency is actually a goal of every programming language on the planet. Some more than others. There is no reason why a language must be either pure bare metal, or else completely oblivious to performance. One other example I can think of is Apple's Swift language which didn't opt for garbage collection, but rather reference counting. Maybe that's a good trade off for writing apps for phones that don't have much memory.
Slashdot Mirror
.. they found someone with a lot of money who wants to die.
This is a crazy leftist plan that will result in either hosting complete cultural rubbish to match the quota, or artificially limiting the catalog to match a quota. For god's sake, end this totalitarian EU before its too late.
Took a look at Julia. Seems like a really nice language. BUT... every time I see a new language I can't help but think every new language is doomed to reinvent Lisp, but badly. Other than the typical hatred of prefix notation, what does Julia hope to give me over Lisp or Scheme?
If you're going to deliberately obscure your code, then there is no hope for you anyway. I can see lots of specialist applications where allowing unicode could really help readability. Would I advocate using it? Probably not. But I think it should be allowed.
In terms of tight math loops, you're right C is hard to optimise. However if you want to write an OS kernel, what else are you going to use? Those details you specify in C suddenly seem necessary to keep tight control. We don't for example want our OS kernel doing garbage collection. Or at least I don't think we do.
C++'s ambiguity between >> as bit shift and templates is a known defect in the language. As for newlines, I don't see that issue as significant as spaces, being whitespace. Every editor in the world knows how to look at a newline. Not so for tabs and spaces.
Really. What language is pure OO in your estimation, and why is that good? And what is this crappy Java database format you're talking about?
Not so much sea level rise as risk of sea level rise. The news flow about sea level rises is hurting values more than actual sea level rises.
They could put their ads in the streams or put requirements about the developers putting their ads in by specification. But they don't. I don't know what they're on about, but if the 3rd party apps become unusable, I won't bother with Twitter anymore. It's not like they even have a Mac app, and their apps on other platforms are marginal in quality.
I think that was an appendix on the anti-global-warming bill.
Maybe, but do they need cooperation from message companies for that? Just trace IP packets.
Knowing how computers work I would have zero sympathy for a computer begging for its "life". However, I would be amused enough to hear it out to find out how clever the programmer was.
I don't know what Amazon is replacing it with, but I'm surprised that SQL databases got so big and stayed so big for so long. There are nice things about them, there is no doubt. But there are so many horrible things about them. Why hasn't Oracle moved with the times? Why haven't they researched and created something better after all this time with all that money?
Growing the market by selling $20 android phones in the Congo is not meaningful market share gains. It's imaginary gains.
Depends what kind of user you are. For simpleton users, there is no lock-in. For me, I have quite a bit of lock in because I rely on quite a few important apps. I'm also locked in by iTunes, Macs, iPads, AirPods, AppleTV and other things. Sure I could move, but the number of comfortable things I'd have to replace is painful to think about once I start thinking about all of it.
I hope Apple isn't going to a vertical keyboard. This would be incredibly stupid for a number of reasons. One being that video watching is a major use (maybe even THE use case), and vertical would suck.
The excuse given for iPhone 7 that the case isn't big enough for headphones doesn't wash either. Apple's minimalism is going too far, and I'm not sure how much more I can stomach.
Apple didn't "admit" that only a small percentage were affected, they tried to gas light us that only a small percentage are affected.
Since I actually read the book, I know what happened. I'm sure the director read the book, so what he thought happened is also no mystery.
This is all fear mongering. There are reefs in the world with water FAR hotter than the great barrier reef. Despite what researchers who benefit from government funding would like you to believe, there is far from agreement that the reef is in any way in trouble.
I don't think they want to drive the price down, even of the artificial ones. They just want a piece of the action.
This is a metaphor for the endless war between progressives and conservatives. Progressives think they know better and want to "do good" and change the world. Conservatives think that systems are complex and your efforts to mess with them will have unintended consequences.
Starting from scratch is really really hard.
It is a flaw. Unix makes files and text the user API to the system, and these things are inherently untyped, unchecked and unsafe as APIs. Nobody would design a serious programming language or API like that.
Now you may say, yes but it's quick and easy. It is, but it's possible to make a system both quick and easy as well as unfragile. Lisp machines come to mind as an example.
Oh I don't know, it's pretty bad. It doesn't solve any of the things that inevitably come up, like what happens when you change your classes, how do you migrate the legacy data? It's not bad if you're a school student hacking some rubbish. But in the real world it's pretty useless.
Efficiency is actually a goal of every programming language on the planet. Some more than others. There is no reason why a language must be either pure bare metal, or else completely oblivious to performance. One other example I can think of is Apple's Swift language which didn't opt for garbage collection, but rather reference counting. Maybe that's a good trade off for writing apps for phones that don't have much memory.