alexandernst

So... what happens now with all the employees that have stock options?

Does it have an actual debugger already? Or are we still stuck with xdebug?

I'm not really sure why this comment is getting downvoted, but literally every single thing in that post still holds true.

Why KDE keeps rewriting every single component every few years? Is that because of improper design/planification or because of bad implementation?

It's very hard to evaluate what's actually going on here. This "post" could perfectly fit in a tweet. No details whatsoever, no details about wether they tried to reach to paypal support and if they got any replies. I'm surprised this isn't flagged.

Explain to me as if I was your 50 years old parent: "What is that Bitcoin money and why I should use it if that 'exchange' thingy can loose it and they won't recover it back? I know my current bank will recover all my money if they get robbed."

Take for granted that I (your 50 years old parent) have near zero knowledge about technology and I just won't use my own wallet and what not.

Because it's just not ready yet. It doesn't cover all the needs it must cover in order to be considered superior to X.

At least that's the only reasonable explanation I can find.

The screenshots link is somewhere in the middle of the page: https://github.com/cnjinhao/nana/wiki/User-Works-using-Nana

Do you plan to write some type of integration with common frameworks (Django, RoR, etc...) in order to be able to skip the entire process of creating entities, relationships, fields, validations and so on (because a team of developers would normally spend quite some time doing exactly that on the backend, it seems like a huge waste of time repeating this work just to scaffold a SPA).

Also, who is this oriented to?

I have mixed feelings about this. Is that a good thing? Should we now get back to writing Java UIs and then just compile them to javascript?

I'm curious to know what OS his phone has and how did they managed to hack into it.

I'd like to know why this is being downvoted.

You had one job...

Indeed, but it matters how much of the data you want to recover and how fast you want to recover it. Getting 100gb from glacier is not expensive at all if you can wait a couple of days.

As cool as this could be, this service is not passing any company-grade backup quality requirements. Also, the price is a complete no. Not because 5€/m is much, but because 5€/m can get you hundreds of GBs of storage in AWS Glacier, with contractual guarantees about your data, how it's managed, etc...

Basically, this is a toy. Use it as a toy, not as a service where you'd actually put your company files.

That said, good job!

How do you manage your ".Trash" folder? Who is in charge of deleting it's content? Do you do it periodically or based on some other event?

What is the usual behavior of any security service? How do you know what is normal and what is not normal if you don't have any actual knowledge about this subject? For all we know, this might actually be the usual behavior.

I love all the "this doesn't sound like a CIA operation" comments.

What do you actually know about anything CIA-related that makes you believe you know if this or that is or isn't a CIA thing?

The biggest BS of the year...

> What is your point exactly, that developers use new features of APIs/libraries?

Exactly. We use whatever new standard makes our live easier. If Firefox or Edge don't support that standard (because they are always lagging behind), there's not much we can do (except going the hard way and implementing workarounds for each browser, which is a no-no most of the time, because of lack of manpower/time). "My website requires Flex support" is pretty much the equivalent of "My game requires DirectX 11".

A standard is whatever goes into https://html.spec.whatwg.org . Period.

CSS Flex is a standard. If Konqueror, Firefox, Edge, or whatever other browser doesn't support it (I know they support it now, but that wasn't the case 2 or 3 years ago), it's not any of my business. I'll keep using Flex because it's an accepted standard. And my webpages will work on any browser that supports that standard. If that means that my website works only on Webkit-based browsers, well, then that's really not up to me to fix, isn't it? That is something that the people behind other browsers should fix, by implementing "Flex".

I see games that are only for 1 OS. And most of the games won't behave the same way running on AMD than on NVIDIA. Also, most of the games require at least XYZ version of DirectX. So, yeah, I'd say your argument is kind of flawed.

And sure, I'll do whatever I want, or whatever my limited time allows me to do. And if that means supporting only the browser with major quota (like games running only on Windows, because that's what has major quota; using your argument), so be it.

Sure. But you're missing a point here. IE6 was bad because it didn't follow any standards. You had to, literally, "code the IE6 way".

Chrome on the other hand is starting to be a problem because it's too damn fast at implementing new stuff (which are accepted as standard). Web-developers then start using those new features and the code they write suddenly doesn't work on other browsers, because those browser just don't support those new features yet.

That's why we got webpack. That's why we got babel and polyfills. And that's why frontend development sucks a lot lately. Because you have the choice of doing X the easy and fast way, that currently works only with Chrome, because no other browser implemented that yet. Or, you can do it the hard and slow way, that works with all browsers.

And this is not something that I'm pulling out of thin air. This has been discussed several times here, in HN.

Not even sure how you got from "let a dying men take some marijuana" to "return slaves" ...

Another issue, IMHO, is the fact that every time somebody proposes some change, for example Gitlab + Gitflow instead of sending patches in some awkward format, via mail, there are a few people that already have their own workflow based on (probably) mutt combined with 10s of scripts, and they don't really want to change their workflow for the greater good; instead, they'd just find reasons why the new proposal sucks and keep using what they already have.

I'm sure this thing would have happened in the exact same way even if the guy was in his home.

Just my 2 cents: Apple currently offers a great user experience in terms of app quality, stability, design, etc... That's because they have a total control over what can and what can't be uploaded to their app store. They run extensive analysis over each one of the apps that are being submitted to the app store and they reserve their right to reject an app even if the slightest bug occurs. That, at the end of the day, turns into a very positive user experience. My question is: Would it be actually good for the end user if Apple is forced to lose control over the app store?

Just my 2 cents: Apple currently offers a great user experience in terms of app quality, stability, design, etc... That's because they have a total control over what can and what can't be uploaded to their app store. They run extensive analysis over each one of the apps that are being submitted to the app store and they reserve their right to reject an app even if the slightest bug occurs. That, at the end of the day, turns into a very positive user experience.

My question is: Would it be actually good for the end user if Apple is forced to lose control over the app store?

Does that mean that it will work with the newest Edge based on Chrome? Hmmm... the entire switch to Edge might actually benefit Microsoft

I used to use Windows and Linux for a very, very, very long time. Never even thought "hey, those fonts don't look quite as good as they could". Then one day I tried Mac. Period.

Oh boy, ever since I just can't use anything else because of the fonts. It visually hurts my eyes.