In all of your condescending[1] comments, you have forgotten to actually articulate what your reasoning is. These are as close as you got:
Dart doesn't have the open, cheerful intentions
Google's overbearing intention is obvious
flawed language
this one is doomed to fail
forced down our throat
[1] I'll Identify these on request. They're unwarranted, counter-productive and rude.
Oh, why not? I wouldn't mind watching a highlight reel and you seem so gleeful.
---
I think my reasoning throughout this page has been more or less articulated, but I suppose I might try for a compact representation.
What exactly do you think is going to happen with Dart?
Is Google going to add Dart to every Chrome install? Sure, maybe. Will so many developers cry out that Safari and IE will also be forced to implement Dart runtimes?
Is every single browser going to run Dart because Dart will have made such a compelling case that it and it alone is preferable to javascript?
Why not python? Why not C, Java, Scala? We could be running those languages in browsers just as easily as we might run Dart.
Do you think Dart is that amazing? Do you think Dart is just so wonderful that it'll unite the programming world as never before?
No.
Even Google's pet framework is divided and recoiling.
The problem isn't that Dart has to compete with javascript, it's that it has to compete with every other language out there, and it's just not that special. Why Dart? If we're going to be serious about ripping up browsers, why Dart?
Now, I maybe should make it more clear: I don't have any problem with Dart as an experiment, Dart as a transpiled language, or even Angular.dart.
But Google doesn't get to decide the future of the web just because it has a bunch of fancy language designers. Google is trying to shove Dart down our throats, and it's not working, and it's not going to work.
Dart will remain a transpiled-to-js language for a time, and then fall off the radar when it's clear that it doesn't transpile to js very well. The alternative is a fantasy.
You claimed that Dart is a flawed language. Substantiate that claim. Basic stuff here. If you can't, I must assume you're a troll or have no clue yet somehow think you do.
> Do you think Dart is that amazing? Do you think Dart is just so wonderful that it'll unite the programming world as never before?
The world isn't black and white. Dart doesn't have to be perfect to be a viable alternative to JS.
> Even Google's pet framework is divided and recoiling.
No, they both thrive and benefit from the other. It is a feature. The same thing is happening with Polymer.
> Why Dart?
Take a cursory look and you'll find some arguments for Dart but I would think you would have covered this before having such a strong opinion.
> Google is trying to shove Dart down our throats
Said multiple times. Substantiate please.
> fall off the radar when it's clear that it doesn't transpile to js very well. The alternative is a fantasy.
So you know more about dart2js capabilities than the creators of V8 and Dart? This is the condescending and arrogant attitude I spoke of.
I was echoing OP (the one who was bemoaning snark and cynicism). Read his paragraphs. Flawed doesn't mean crippled. There are things about Dart I like.
A language can't be perfect.
>No, they both thrive and benefit from the other.
Pay attention to negative feedback. Some substantial portion of AngularJS devs are unhappy.
>Take a cursory look and you'll find some arguments for Dart
I'm not arguing for Dart's existence here, I'm saying Dart has absolutely no chance of securing the browser's runtime over javascript. Why Dart, why not Go?
>So you know more about dart2js capabilities than the creators of V8 and Dart?
Say whatever you want about benchmarks, Angular.dart is either a terrible port (quite possible) or Dart's transpiler isn't on the level of CoffeeScript or TypeScript.
>This is the condescending and arrogant attitude I spoke of.
I'm asserting something grand and sweeping that I think to be true. Get over it or walk away.
> Some substantial portion of AngularJS devs are unhappy.
Define "substantial". I've seen some complaints here that AngularDart has, and will, take away from AngularJS, which, again, is unsubstantiated. It's counter to the evidence and the likelihood that the groups working together will make both better.
> I'm not arguing for Dart's existence here, I'm saying Dart has absolutely no chance of securing the browser's runtime over javascript.
Uh, you've expressed "cynicism [...] over Google's waste of time" and called Dart "pretty flawed", which you haven't substantiated yet. If your were merely expressing skepticism over Dart "securing the browser's runtime over javascript", there wouldn't be a discussion here. Brendan Eich did that for you a long time ago. I'd contend that it doesn't really matter as long as dart2js can fulfill its goals; however, I'd still maintain a wait-and-see attitude about how we'll see DartVM used. There are some very interesting possibilities.
> 173KB. This is ridiculous.
Substance! Thank you. Dart is pre-1.0. It's being worked on. Also, notice at the bottom of that page:
We want your help, especially if you can make update
@MirrorsUsed in main.dart to generate a smaller binary.
> Get over it or walk away.
No, I won't. The attitude isn't conducive to civil discourse and not welcome here so I'll continue calling it out where I see it. I'll take the upvotes as confirmation that others agree with me.
You've got your unsubstantiated opinions and will continue making these "sweeping" claims so there's no point in continuing here. It leaves little room for meaningful discussion, unfortunately.
It's telling, to me, that the first argument of mine you take seriously you handwave over by vaguely saying it will get better and it can be fixed.
I'd place a bet that Dart is about as good as it is ever going to be.
>I'll take the upvotes as confirmation that others agree with me.
Sorry to disappoint you, but I've got upvotes, too.
>The attitude isn't conducive to civil discourse and not welcome here so I'll continue calling it out where I see it.
Whatever floats your pompous self-righteous boat.
I may be curt, strident, and critical, but you don't really have high ground when it comes to condescension. You went straight to childish insults. https://news.ycombinator.com/item?id=6679901
When I disagree with someone I don't directly call them stupid or immature. (Well, usually.) I may speak and act as if something I believe strongly is obvious, and I may not mask my disdain for the ideas expressed. There's nothing wrong with being wrong, but I'm not going to hide the fact that I think you're wrong.
You seem to have a problem that someone a) disagrees with you, and b) says so confidently and forcefully. Again, get over it or walk away. If I'm so wrong and so boorish, you are under no contract to continue.
You can't change me and I am not your responsibility.
Fortunately I think you've finally clued in ("so there's no point in continuing here"). I've certainly spent enough time on this. Later.
> Whatever floats your pompous self-righteous boat.
> I may be curt, strident, and critical, but you don't really have high ground when it comes to condescension. You went straight to childish insults. https://news.ycombinator.com/item?id=6679901
What exactly are those instructions? You or your friend have a misunderstanding. This dual-implementation will benefit the project as a whole (whether you prefer JS or Dart). That's what this is about, not to make JS a second-class citizen because evil Google wants to shove Dart down your throat.
> it was fairly obvious that some of the guys didn't want Dart in there
I don't think it was obvious. It may be true but they were uncontroversial comments on a controversial topic. The language and DartVM aren't ready for Chrome, right now. You'd hear the same from the Dart team.
> we don't need a language to replace javascript
Absolutely... in the same way we didn't need Python, Ruby, C++, Java, Clojure, Haskell, etc. In fact, I'd say we needed those less considering the enormous choice on non-web platforms.
Certainly possible but remember that "contractor" and "employee" have legal definitions. You can't "just" call an employee (by the legal definition) a contractor.
(Edit: I see ljoshua beat me to the possibility for issues here but it's important to emphasize that it can be done, just play by the rules to avoid trouble down the line.)
Actually there are. And it would be great if there was just a checklist that you could go against, but the best we've got is this page [1] from the IRS and some legal interpretation. I agree that the positions could more clearly state that it was a contracting position, but it looks like more of an employer-employee type job board than an eLance type deal to me. So they just have to be careful.
> I wonder if enough people avoid new Google products due to shutdown fears [...]
I doubt it. That attitude is mostly a HN/geek thing. I like that they're willing to try things and test for viability in the real world. I'd rather have something and for it go away than to never have it at all. (And yes, I do understand the frustrations with Reader but I wouldn't go back in time and never use it from the start)
This wasn't about Reader specifically. Google has shutdown a lot of products. The latest being Google Checkout, which makes people nervous of building their business on Google's software. Since this service is paid, I could be netting a lot of money through it, only for it to fizzle out.
> Since this service is paid, I could be netting a lot of money through it, only for it to fizzle out.
But that's true of any service from any company. If I'm a stay-at-home mom making some extra cash on Helpouts, I have a very different risk profile than a doctor who closes down his practice to see patients exclusively through Helpouts. The stay-at-home mom might not be happy about a shutdown but she still "[netted] a lot of money" whereas the doctor might have destroyed his/her career. Every individual/company needs to assess their own risk and take the appropriate risk-mitigating actions.
The point I'm making is that the damages from a Google service shutdown are typically very low or easily mitigated (Google Checkout being no exception) and every service should be evaluated on an individual basis with your risk profile. If the value you are getting from any service is lower than the damages that would result from a shutdown, don't put all of your eggs in that basket; if you do anyway, get some contractual guarantees and be confident that they will be fulfilled.
They have deprecation policies in at least some cases. They may not be unconditional guarantees but they're still just risk factors to be evaluated individually. I have no problem with the risk averse avoiding any services for their own reasons but it's gone beyond that in many cases here on HN to pure FUD. In any case, you've taken that clause out of context.
> When the boss disrespects customers in front of his team, that sets the upper limit for how well customers will be treated by the company.
A single incident sets the upper limit? We don't know what kind of example he sets on a day-to-day basis. Customer service is a mentally taxing job. If I'm the person on the front line, I'm thinking, "at least the boss understands and has my back" rather than feeling defeated. Some customers are just bad customers; sure, try to understand and sympathize but there comes a point to tell them to "fuck off" (in the appropriate customer-service language).
The only thing wrong here is that it leaked out to the customer.
> I've seen this happen to a few of my friends who hit it big [...] it's like the insatiable drive to achieve that made that possible just evaporates.
This hits many people after just talking about their goals. They get the same good feelings of achievement that lead to de-motivation to follow through with it.
It's not as if the president is an uninterested party. He very much supports the NSA, is in a position of power on the matter and if he's got nothing to hide then he has nothing to worry about, right?
Those things are covered and if you would have taken the time to do even a cursory review before writing your baseless dismissal you would have seen this.
It's clear this is an evolving project. I don't believe Derek Sivers would do a project like you making it out to be and I don't think you have any basis to think he is, even if you don't know who he is.
Just to quickly address some things where you've missed the point: these are entrepreneurs' guides; these are targeted at an American and other non-Asian markets so it's important to answer questions from that perspective, regardless if you think they're irrelevant (you can't know what's irrelevant until someone tells you or you learn from experience); it's amusing that the "contents are a joke" when they address the things you have asked for.
And from above:
> Come on... this is lowly. Just because you have some money to spam-market quick-e-books with doesn't mean you are the arbiter of truth. Hire a real writer, do some real research, and be honest about it. Without quality, there is little point in publishing.
Fail.
Go look at the content before before making such claims ("lowly...spam...without quality") and advising them on their methods. After you've done that, how about focusing on the content?
Sorry for the tone but I can't stand these types of off-base dismissals and ending it with "fail" is just the icing on the cake. Derek Sivers is a respected member of the community that just spent the last nearly two years of his life on this and deserves better than these as the top comments on his announcement.
No, I'm not. I'm sure you can do your own search for "law", "tax", "immigration", etc.
If you had done that, I'd have no issue with a civil critique of the content but to dismiss ("fail", really?), insult ("spam") and patronize ("Hire a real writer[...]") the project of a respected member of the community (or anyone) to the extend that you did, with no basis (you haven't read the book and don't seem to have read the table of contents), has no place here or anywhere intelligent discussion is desired.
In all of your condescending[1] comments, you have forgotten to actually articulate what your reasoning is. These are as close as you got:
[1] I'll Identify these on request. They're unwarranted, counter-productive and rude.