Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:There might not be Proper English (Score 1) 667

by znrt (#49269139) Attached to: Why There Is No Such Thing as 'Proper English'

trying to slow down the fragmentation of the language into dialects

"dialect" is a term used for arbitrary classification. there is absolutely no linguistic difference between what you call a "language" and a "dialect", both are the exact same thing.

language fragmentation is inherent to geographic distribution. there is no such thing as "proper english" unless maybe you are referring to a particular form of english dominant in england at a given time, which is a pretty useless definition in the current world.

dominant languages today have become such through military/economic/cultural expansion, and expansion naturally implies fragmentation. there is no more "english" to speak of, but "englishes" or whatever the plural of english would be in your particular english.

Comment: Re:What's TSYNC ? (Score 2) 338

by znrt (#49210355) Attached to: Google Chrome Requires TSYNC Support Under Linux

it stops new versions of Chrome from running, which is a security concern.

if old versions of chrome become a security concern it's google's responsibility to either provide a fixes or at least effectively warn users, period. has nothing to do with any aspect of any os chrome happens to run on.

So really what's going on is a conflict between organizations. Google wants to move faster than Debian does, and Debian (or at least Ben) doesn't want to give Google special concessions.

it's much like you say but i see no conflict, really. google can have its way, and debian (ben) is just being consistent with being debian. users can have their pick so no problem. responsibility is still clearly outlined and any rogue chrome versions causing havoc will be chrome's fault, regardless of kernel. so google should at least inform the user that they dropped support for platform x so he could pick a different browser. they have done so in the past.

i made this reflection because of you mentioning "security concerns", but i don't know of any in this context. i understand now that tsync allows for cleaner implementation of sandboxing, but if you deliver a sandboxed browser for a platform you better make sure it's indeed properly sandboxed with the api available for that platform at that moment. IF chrome had known security issues with that then debian, being debian, should of course hold it back.

Comment: Re:ABOUT FUCKING TIME! (Score 1) 765

by znrt (#49201263) Attached to: Ubuntu To Officially Switch To systemd Next Monday

lol.

Things Of Interest Blog
Suicide Linux
You know how sometimes if you mistype a filename in Bash, it corrects your spelling and runs the command anyway? Such as when changing directory, or opening a file.

no. never. really?

any time - you type any remotely incorrect command, the interpreter creatively resolves it into rm -rf / and wipes your hard drive.

freaky idea anyway, can't say i don't like it.

Comment: Re:ABOUT FUCKING TIME! (Score 1) 765

by znrt (#49201221) Attached to: Ubuntu To Officially Switch To systemd Next Monday

ubuntu has always been linux for casual users.

well, the initial motto was "linux for human beings" but, well, it's just a catchy motto.

now if you consider what it really means to be "an operating system for casual users" you realize that ubuntu is not at all far from windows or macos on that level, don't expect too much. however, it's free, and it's an entrypoint to more advanced distros. it's still not irrelevant.

Comment: Re: Hard to believe (Score 2) 166

by znrt (#49145147) Attached to: Microsoft's Goals For Their New Web Rendering Engine

No, it isn't, and it never has been. You utterly fail to understand the 'integration' issue with IE.

yes, it is: http://en.wikipedia.org/wiki/S...
you fail to understand the single point of failure issues with ms components in general, not just ie. ie is just an example of having such vulnerable crap open to external access.

granted, i don't know if this still exists in windows 8. i very much guess so, but i don't really care. if you use windows, you should.

Comment: Re:Hard to believe (Score 1) 166

by znrt (#49145119) Attached to: Microsoft's Goals For Their New Web Rendering Engine

> "We needed a plan to make it easy for Web developers to build compatible sites regardless of which browser they develop first for."

Can you even IMAGINE Microsoft saying that 15 years ago?

yes. it's old. ms has been lying and spreading bs and fud since day one. an egregious and sick example of their cynicism in this area is "compatibility mode".

Comment: Re:New jobs will be created. (Score 1) 266

by znrt (#49100291) Attached to: The Robots That Will Put Coders Out of Work

gorgeous.

however, given just an expected output there will be lots of conforming inputs. you still need to figure out which of those randomly generated functions not only produces the same output by chance, but actually conveys the expected operation. in short, you would have to run the test for all possible inputs.

that's for a single unit test. imagining integration test just gave me a shudder :)

Comment: Re:New jobs will be created. (Score 1) 266

by znrt (#49100227) Attached to: The Robots That Will Put Coders Out of Work

the demand of functionality however is also getting more. did you expect anyone to ask you to do elgamal encryption on a cell phone browser back in the day?

there will be always problems to be solved. the trivial stuff you can give to 'key punchers'. or robots, for that matter, once we have created the right tools. i don't think we have. article is bs (if it is even remotely related to the summary. didn't bother to read)

Comment: Re:Ummmm.... (Score 1) 319

by znrt (#49100095) Attached to: Java Vs. Node.js: Epic Battle For Dev Mindshare

you can, just don't expect it to be widely adopted. plus your niche shouldn't have security and usability concerns.

also, be aware that applet support isn't likely to last much longer. several plugins aren't supported anymore on the desktop, and there aren't any at all for mobile devices or tablets. since java 1.7ish even running signed privileged applets on supported browsers on desktop is a pain. in short: maintaining applet support is problematic and nobody seems to bother anymore, specially since there is no benefit: js can now handle most of what applets did in the browser in the past, right out of the box and better.

there still are a few very specific usecases for applets like, for example, to access smartcard readers from a webapp. but even then, applet maintenance and deployment is hardly optimal and you'd probably will end up ditching the whole idea and lookig for a workaround.

and of course you don't have to learn "every language out there" if you don't want. however, if you want to do stuff for the web today (that's what applets were for) you simply won't get away without learning js. it's not optional.

Comment: Re:Ummmm.... (Score 1) 319

by znrt (#49083377) Attached to: Java Vs. Node.js: Epic Battle For Dev Mindshare

My point is, node.js might itself be fine, but when the software that relies on it is so badly broken as this,

very true for the "npm" constellation, and possibly for the particular projects/products you have experienced. but this just reflects that it's a new platform and a hyperactive ecosystem. sure it has it's fair share of hipster crap, but just keep looking, there's quite solid stuff too. and there is a lot you can do with pure node.

besides, running java applications on linux has sufferd the very same problems for years (hell, it still does sometimes!), even when java was more mature back then than node is now. and you sure will remember what a complete dependency nightmare java was before maven was adopted.

The amateurish approach to the software using it taints it.

well, i'd say just avoid that software and ... it's my impression that you are overestimating what "professional" means nowadays. :-)

A committee is a group that keeps the minutes and loses hours. -- Milton Berle

Working...