21–30 of 175 posts
Many Developer think that they are the best developer in the world and this kind of people dont honor others work.
Since i use github, i see that not everybody think like you do (in the past i agree with your statement).
Brython has bubbled up on HackerNews several times. It might not be "not impressed", just "not impressed anymore." Edit: Added quotation marks.
This. I didn't say anything on the Brython post from yesterday, but I certainly wasn't very impressed having seen it at least twice before on HN and what with the dozens of foo-to-JS transcompilers that have been cropping up lately. I didn't upvote, I didn't downvote, and I didn't comment though. Maybe the lesson is "if you don't have something nice[1] to say, don't say it at all". [1] or meaningfully constructive, a…
Are the examples given by the author really that worthy of respect? If you write yet another unnecessary Foo to Javascript translator, or over-complicate your code to show off how well you know the dark corners of your chosen language (both examples given by Chris), should people really be impressed? And if people aren't, should they put on a fake smile and pretend to be?
Are the examples given by the author really that worthy of respect? If you write yet another unnecessary Foo to Javascript translator, or over-complicate your code to show off how well you know the dark corners of your chosen language (both examples given by Chris), should people really be impressed? And if people aren't, should they put on a fake smile and pretend to be?
In regards to devs, I am a hacker (my criminal record proves it), but you'll always come across people who are ignorant in what they know and unwilling to be open to change or something they didn't have a hand in.
ALL OF US as coders need to be open to new libraries, code bases, languages, and always willing to learn, but I think it's inherited with our skills that we look for holes, errors, and other ways to optimize...to the point that it comes off as an attack instead of criticism.
If you link on HN, EXPECT criticism (constructive hopefully), and just ignore the ignorant trolls. A real coder knows how to give supportive criticism, and credit where credit is due....Not sure if this validates my opinion, but I'm easily impressed though :)
Took a break from HN (and others) for about 8 months at the end of 2012 and start of 2013. The HN I came back to feels very different. Everyone knows better and is eager to prove it by putting others down. Comments are no longer about the OP, but about how the OP is laughable, let me tell you how to do it . So sad.
^ Posts like those? :D
I had missed the first link about a Python interpreter in JS. I too find it incredible and very exciting. I'm not sure I want to manipulate the DOM in Python instead of JS/jQuery, but it could prove super cool to write web workers in Python for instance. The more you can compute in the browser the better. The client is where CPU cycles go to die, we need to change that.
It's impressive from a technical standpoint, and that is in some ways enough.
But why the need to port everything to javascript? I don't use python for things I would write in javascript and unless you are prepared to port all the libraries (i.e. the thing that makes python so useful/fun/awesome) then why? I can just use JS. JS is a language with good enough features. I don't need a python that compiles/is intepreted in JS.
It's less that I am not impressed, and more that I think the effort is somewhat wasted. Of course I still respect the implementer.
Are the examples given by the author really that worthy of respect? If you write yet another unnecessary Foo to Javascript translator, or over-complicate your code to show off how well you know the dark corners of your chosen language (both examples given by Chris), should people really be impressed? And if people aren't, should they put on a fake smile and pretend to be?
Offering a critique doesn't have to be fake smiles, nor does it have to be slagging off. People can ignore posts. Or people can offer calm advice about why something is suboptimal.