ng12

62 ms·

691.
by ng12 7y ago
> they'll produce even more oil than they otherwise would have. The production of oil is not the problem. They produce oil because we, as a society, have placed tremendous value on it. Once we no longer need oil they'll stop pr
692.
by ng12 7y ago
You're also reducing their ability to produce oil safely and effectively, while simultaneously handing more economic power to oppressive OPEC regimes. Weaning ourselves off of oil is the first step not the last.
693.
by ng12 7y ago
Because when they're ineffective oil gets spilled. We have a vested interest in oil being produced as cleanly and effectively as possible until we can lessen our dependence on it. Furthermore, the OPEC countries don't care at all
694.
by ng12 7y ago
> But laws and elections have been singularly ineffective at stopping global warming. And you think removing their access to GCP is going to stop them?
695.
by ng12 7y ago
Doesn't really apply. Oil companies exist because we buy oil -- both directly (fueling our cars) and indirectly (buying produce shipped from South America or clothing shipped from India). Saying "oil companies shouldn't have
696.
by ng12 7y ago
The market is no longer free when China is involved. They'll gobble American market share (and use that market share to further their political goals) while completely blocking out American companies from the Chinese market. Nobody wou
697.
by ng12 7y ago
I really wish HN wouldn't do this except for materially incorrect titles. I find myself trying to figure out if a link/discussion is the same one I've already read after the title has been editorialized.
698.
by ng12 7y ago
Why does this piece refer to her as Ms. Warren instead of Sen. Warren?
699.
by ng12 7y ago
> Not close to fully runtime-less sure, but about as close as you can get. Have you looked at transpiled Svelte code? It's 5-10x bigger than the source code because an entire runtime library is injected and your code is rewritten to
700.
by ng12 7y ago
> a vanilla TODO Vue application with its syntax is much much better to work with a vanilla TODO react app These would be almost identical in structure and design. You're drastically overstating the difference between React and Vue
701.
by ng12 7y ago
Honestly I think these discussions are just pretty low quality. I find that people are pretty good at mis-attributing their success and failures to their tech stacks, especially in a field where there's a lot of novices like front-end
702.
by ng12 7y ago
> 'Vue.Component' and a template string. But the template string is just a string, right? Can you get the same IDE integration while avoiding SFCs?
703.
by ng12 7y ago
I'm explaining why I don't like SFCs because the above poster referenced them as a "pro" for Vue over React. Whether or not you _have_ to use them in Vue is immaterial.
704.
by ng12 7y ago
Correct me if I'm wrong but I imagine that's more for the tooling (e.g. syntax highlighting for my template and styles) than an actual preference for SFCs.
705.
by ng12 7y ago
That's not what I'm saying. What if I have a child component I don't want to put in a separate file? What if I want a child component defined as a closure inside my parent component? What if I want one file that exports many
706.
by ng12 7y ago
> I was hoping for less (or non-at-all) "stringly typing". It's the curse of the template. Once you have them you inevitably start encoding more of your logic in magic-voodoo template directives.
707.
by ng12 7y ago
> Single file components Honestly I think this is a step backwards. How many components my "component" is built out of should be an implementation detail.
708.
by ng12 7y ago
> As somebody who doesn't want typescript support, at all, I relish the lack of typescript support! That's a pretty strange statement. TypeScript support does not mean you have to use TypeScript. It's purely additive by de
709.
by ng12 7y ago
By purchasing heroin/cocaine you are virtually guaranteed to be financially supporting a narco-terrorist group.
710.
by ng12 7y ago
I elaborated below. A mix of the strict one component per file rule and the definition of props as a sequence of independent variables prevents a lot of patterns I use on larger projects.
711.
by ng12 7y ago
> Dont flame me please If you feel the need to include this 4x in your post, perhaps it's a good idea to do some re-evaluating ;)
712.
by ng12 7y ago
Since Svelte props are just variables it's pretty easy to do weird things. Also it's kind of a pain to need to open up a file and read through a dozen lines of code to figure out what the props are. The most important thing is it
713.
by ng12 7y ago
It's cute but I can't recommend it for a project with more than one developer. Lack of TypeScript support and the hacky component model (specifically, Svelte's equivalent of React props) are the two big deal-breakers.
714.
by ng12 7y ago
> the IRS tells me I should believe otherwise If you have NSOs (or pay AMT) the IRS will happily lie to you about the true value of your options.
715.
by ng12 7y ago
This is the opposite of the American dream. Immigrants fled to the US for it's unprecedented social mobility and opportunity. Things being nice for the upper echelons of society has little to do with it.
716.
by ng12 7y ago
> can't use regular HTML, can't use regular CSS, can't use async/await I'm pretty sure I'm being baited here but all of these are categorically false.
717.
by ng12 7y ago
I'd like to see some evidence to back that up. The event loop is one of the few things JavaScript did correctly and it's baked into everything but the most trivial of applications.
718.
by ng12 7y ago
And you're implying asynchronous coding is new to JavaScript developers?
719.
by ng12 7y ago
> Fetch the data you need and provide it to the view. That's exactly what this feature is doing -- making the view layer more flexible in how it responds to the data received.
720.
by ng12 7y ago
Can you elaborate? At a minimum vdom is just doing work you would have had to do manually with DOM apis.

More ›