...Sorry.
1,728 karma · joined March 22, 2013
Q: "What do you call a mermaid's undergarments?" A: "Algae-bra"(Aug, 13)
Q: "What do you call Germany's currency?" A: "Ger-money"(Sept 23-13)
saved comments:
https://news.ycombinator.com/item?id=6443135
...Sorry.
I haven't used VS Code since the beta, but it can do that now? Wow. I should give it a try.
And frankly, a significant portion of jquery usages are a very limited set of functionalities: selection, class manipulation, some visible on/off, AJAX and promises. A lot of those don't necessarily need jquery[2]. Some hard-core guys go so far as to separately download only modules[3] which works.
Honestly, I wouldn't mind calling a significant portion of jquery to be "pure javascript" as it lets me not worry about browser compatibilities and pleasant stuff that should have been part of standard library. ES6 is supposedly fix most of the complaints, but whether browsers will support them or not is a different question.
[1] https://mathiasbynens.be/demo/jquery-size has a nice tabular info on how large jquery file sizes were.
[2] http://youmightnotneedjquery.com/ is a widely cited source.
[3] https://github.com/jquery/jquery/tree/master/src, go nuts.
> I don’t feel the “problems” CSS preprocessors intend to solve are serious enough to warrant the cost, i.e. to me the solution is worse than the problem.
I don't think CSS preprocessors solve any problem per se, insomuch that C preprocessors solve any problems - they just help the code without introducing extra syntax to the core language.
> I want absolute control of my CSS, which means I want to work hands on with it, and see exactly what will be sent to the browser (well, before it’s minified and gzipped, of course). If that means seeing the same declarations repeated in several rules, or having to see what vendor prefixes look like, so be it. To me, WET CSS is much more understandable and maintainable than DRY black box pseudo-CSS.
I don't see how this argument is different from refusal to use any language other than C for complete control. While it does give you complete control, often times it may not even be worthwhile. In fact, SASS constructions are well-defined(enough) that most of time, you can derive exactly how the resultant CSS will look like; of course, some minute optimization may be required but the same argument can be made by pointing out that dlls exist.
> I don’t want to learn and depend on a non-standard syntax to wrap my CSS in, making it require compilation before browsers can understand it. Neither do I want my colleagues to have to.
Unless your team uses two different method of compilation on one environment(i.e., agreeing on which implementation to use), I doubt there'll be any problem with consistency. If you do use different compilations so that standardness matter, then you have a different problem.
> I want my source CSS to be deployable at all times, albeit in un-minified, un-concatenated form. If my build process fails, for whatever reason (like an unpublished npm module), I can deploy the source CSS as an emergency solution. Performance may perhaps take a hit, but a slightly slower site is likely better than a site with broken or no CSS until the build process can be fixed.
This is a non-sequitur on a hypothetical situation on artificial emergency.
> I don’t want to have to wait for compilation before seeing the results of my CSS changes. Processing time may be anything from negligible to frustrating, obviously, but if it takes longer than the time it takes for me to switch from my code editor to my browser and reload the page (≈1s) it’s too slow.
filesystem watch generally handles the auto-compilation, and am I the only one who edits css on-browser first before editing files on CSS sheet? If the only way to edit styles on web page is editing the source and reload, this method will definitely cause much more frustration on dynamically generated applications.
I can sort of see where this person is coming from, but I would say the benefit outweighs the cost here. Again, personal preference, but I would rather have my team employ preprocessor just for variables and palette from designs.
This is our Deep Blue moment folks. a history is made.
Granted, most of actual git activities are better done via command line, except for chunk editing.
Just one chagrin I have with sourcetree is the lack of linux integration, despite obvious demand: https://answers.atlassian.com/questions/149631/sourcetree-fo...
What I find lacking in such comments, though, is some explanation on why and the suggested alternatives. Would you mind sharing why? Java/C# were the hot things of 10-15 years ago and people still make a living out of it. It sounds like an argument for classic Red Queen problem where the only winning move is not to play.
It's stipulated that 7 will be the new XP, and 2015 may be the first year to start XP-ization of 7.
Still, a readable manpage alternative is always welcome!
"By 2010, one in four new jobs will be “technically-oriented,” or involving computers. However, women still lag far behind in earning computer technology degrees and working in computer technology-related professions. High school girls represent only 17 percent of computer science AP test takers and college-educated women earn only 27 percent of bachelor’s degrees in computer science (down from 37 percent in 1984) and 16.3 percent of doctorate degrees in computer science. Overall, women comprise roughly 20 percent of IT professionals. (“Tech Savvy: Educating Girls in the New Computer Age,” American Association for University Women, 2000)" [1]
Barring the "down from 37 percent" part, it tells me that 17% of female high schoolers take AP computer science, but actually a higher percentage of women end up with a CS diploma. It's very thin connection but that does raise a question that affirmative action lets in more women.
[1] http://www.civilrights.org/equal-opportunity/fact-sheets/fac...