I was very frustrated when I tried to move to gulp+sass+babel+uglifier tool chain, It took me an afternoon to set everything up before I can write any actual code.
The whole thing looks like to be designed toward make big and long-term maintained website, not toward helping you to hack up throw away site quickly.
Stuff like gulp, after I installed it globally, I still have to install it per project, which makes little sense to me.
It used to be just "compass init; compass watch", and start write stuff, uglify JS before deploy, then done.
I still hates JS, I don't get why a language once hated by everyone, now is sexy again.
PHP in contrast, have improved a lot since 5.3, and it actually quite fun to write these days.
PHP is the diamond in the rough. Don't let all the bad tutorials fool you, beneath is a great platform where you are truly productive.
You get far by only having PHP and you get twice that by only installing composer.
No insane build steps, no running server process that needs to be hot reloaded, composer is faster relative npm, decent typing system and built in development web server.
To make PHP a superb language(okay, a better language :-) I wish for three things.
* Typed callable signatures
* Function autoloading
* Generics
Looking forward to the possibility of a jit in PHP 8.
In Visual Studio you go from 0 to "Hello world" in about as much time it takes to download and install the behemoth. And if you're having trouble with some part of the toolchain you'll know that everybody using the same version of VS will have the same tools so there's a very clear way to find help: "Visual Studio {$version} {$description_problem}".
While ASP.Net used to be (pre MVC) the shitty enterprise sloth that was holding you back to any serious quick development now a full web stack looks like more work to maintain than using VS. I think that should alarm some people.
Things should "just work" while I am getting things done. And if not there should be a reliable way to troubleshoot it.
PHP definitely got better while it still has a lot to improve. It just looks a lot less ugly when I see it, actually smart sometimes.
You should be able to use one IDE with full autocomplete (not autoguess) and a full stack going from project creation to project publishing. Otherwise your time is wasted.
When you install a package locally, executable files get added to node_modules/.bin. So you can run gulp using node_modules/.bin/gulp. Also, npm scripts automatically have that directory added to their path when they are run, which lets you use npm run to access things like gulp.
This makes me think of sidewiki. Will many people really go find rebuttals and contribute back to the original page? It seems a little bit too much of work.
So far we are getting very promising numbers. The main difference betwen us and all of the annotation services which have come before us (around 50 on last count, thanks to Hypothes.is), is that we are page level. We connect one URL to another. It is so simple your grandmother could probably do it. The previous versions were all line-level, meaning that you had to highlight text and then write your comment, or connect to another page etc. It was overwhelming and confusing. rbutr requires you to press two button, small descriptive comment and tag. You don't need to be an expert on the subject matter or anything. You just connect the two authors who claim to know about it to one another...
When you upload a file, you just licensed Google to go whatever they want that they think is going to promote or improve their service for unlimited time.
IMO, the first sentence "You retain ownership" actually means nothing to them.
I'm confused, if "knowledge of infringing material and do nothing about it" cause you have no safe harbor. Any big content site like YouTube must know some of it's users are abusing the service, but they're more likely to handle it after there's complain.
Or how can you tell whether a file is copyright infringement or not? censoring all uploads, non sense.
Huge difference between knowing there's some infringing content somewhere versus reviewing, rewarding, and noting an uploader because of "10+ Full popular DVD rips (split files), a few small porn movies, some software with keygenerators (warez)." Censoring all uploads is hyperbole.
YouTube is probably not the best example, because they built their userbase on allowing copyright-infringement until they were big enough to negotiate directly with the content owners. If Megaupload had sold out to Google or some other legit business with deep pockets, they would not have been busted.
Why it's crappy? Why you doubt it's legel? If you doubt so than maybe hacker news is also illegal because it looks like a raddit clone. (of course not)
HN and reddit are similar, but they also take different approaches. Coordino advertises itself as a "StackExchange clone" in the page <title />. It seems to be copying as many aspects of StackExchange as possible, down to the look and feel.
I called it "crappy" because it is much less polished than StackExchange. Perhaps the pejorative is unfair.
The whole thing looks like to be designed toward make big and long-term maintained website, not toward helping you to hack up throw away site quickly.
Stuff like gulp, after I installed it globally, I still have to install it per project, which makes little sense to me.
It used to be just "compass init; compass watch", and start write stuff, uglify JS before deploy, then done.
I still hates JS, I don't get why a language once hated by everyone, now is sexy again. PHP in contrast, have improved a lot since 5.3, and it actually quite fun to write these days.