HNHacker News
TopNewBestAskShowJobs

secoif

840 karma · joined April 19, 2011

submissionscomments
secoif··on Frameworks are for hacks, libraries for seeds
If you're going to not use a framework, then end up creating a framework, then you've defeated the point of not using a framework and you might as well have used an existing framework and saved yourself the effort.

It's entirely possible to build applications without infecting it with anything that looks like a framework if you resist the urge to create unnecessary abstractions and keep coupling to an absolute bare minimum. Keep it simple and focus on the task at hand.

secoif··on Io.js 1.0.0
Node is moving to semantic versioning: http://semver.org/

In this scheme, version number is not an indicator of stability.

secoif··on Io.js 1.0.0
Google's v8 is the JavaScript. io.js provides APIs for performing disk and network io, using v8.
secoif··on Is JavaScript getting worse?
Also removes return statement for 1 liners. Reduces clutter of anon functions, especially when you're chaining a bunch together

e.g.

ES5

    users.map(function(user) {
      return user.name
    }).filter(function(name) {
      return name.length < 30
    }).sort(function(a, b) {
      return a.length - b.length
    })
vs

ES6

    users
    .map(user => user.name)
    .filter(name => name.length < 30)
    .sort((a, b) => a.length - b.length)
Contrived, but typical example.
secoif··on Approachio – Wisdom of the Crowds
Is your sign up form huge?
secoif··on Sugar: A JavaScript library for working with native objects
This tool is absolutely amazing and a great idea… but has a big caveat: you can't sandbox it because it extends prototypes, so unfortunately it's entirely 100% unusable in node because it breaks module encapsulation. Node allows multiple versions of the same package to exist simultaneously, so if one package depends on sugar@1.0.0 and another on sugar@1.5.0, the version that is used to extend the prototypes is entirely determined at run-time – and could even change at run-time.
secoif··on Commander.js – Node.js command-line interfaces made easy
Commander.js is a few years old and adopts the name from a ruby project of the same name (from same author) from 09.
secoif··on MQTT: An Implementer's Perspective
This comment's sales pitch tone really comes to a crescendo around "Have you had a chance to look into dweet?", just FYI you may want to avoid this type of language in the future.
secoif··on Jsfmt – Like Gofmt, but for JavaScript
Nope, the point about adoption is spot on since you can already do this with esprima and other tools (e.g. substack's falafel/burrito or grasp) which already have a community. Outside of api flavour, they do the same thing. The differentiating factor is primarily which one will have stronger better community support.

My prediction is that since this is "go-flavoured", it will face some (unwarranted) adoption resistance amongst influential JS devs. This tool might attract new devs into the code manipulation space and they'll eventually converge on to the tool with strongest community support.

secoif··on Ask HN: Our Kickstarter project is failing
Overall lack of professionalism is the problem. It looks like a highschool student project. Art (not just the game-art) is sub-par (sorry!). Next time you should involve someone who knows how to assemble a professional presentation. Knowing when to call in help is the best skill you can learn.
secoif··on Why the (CoffeeScript) arrow matters
> Generally it's considered idiomatic to just avoid named functions altogether.

This is not idiomatic. Many developers only use named functions.

The obvious reason is they make stack traces far more readable, though you can get around this by naming functions anyway:

  var myFunction = function myFunction() {}
The hoisting 'nuances' you decry are a boon. Hoisting means you never have to worry about the order functions are declared – especially useful in cases where your functions call each other. You also get another avenue to declutter your code by pushing any crufty utility functions to the bottom of the page.
secoif··on How I Work Around The require(“../../../../../../../”) Problem In NodeJS
Anyone with this problem is most likely working on a horrible monolith. You have far too much nesting and you're simply hiding the symptoms of a greater problem. Flat > nested. Simple > complex. Law of demeter also applies to reaching and in/out of folders. Break your app into more smaller modules rather than sweeping your mess under the rug.
secoif··on Missing Person, Luke Arduini: Yahoo Programmer. Please help find him.
Shame there's no way to sticky posts during emergencies.
secoif··on Teleportation on the command line
auto jump (or z) is so incredibly useful it should be built into the terminal. changed my life.
secoif··on Atlassian Seeks Domicile Move to Pave Way for U.S. Initial Offer
Are other AU companies feeling the same way?
secoif··on Bzr is dying; Emacs needs to move
What does this have to do with integrity?
secoif··on What still sucks about front-end web development
There's little point complaining about the current state of front-end development while we're on the cusp of the next generation of front-end technology.

e.g. Non-semantic HTML is avoided with Shadow-Dom + Custom Elements + aria attributes & JavaScript library management is mostly solved by ES6 modules.

secoif··on The Future of JavaScript MVCs
gotcha. understood.
secoif··on The Future of JavaScript MVCs
The flame graphs are meaningless and misleading: om's graph is only looking at 260ms of data, while the backbone's is looking at 1200ms.
secoif··on List of minimalist frameworks
That's exactly what it is, and that's the beauty of it.
secoif··on List of minimalist frameworks
A fantastic example of this (in javascript) is trending right now on hackernews – myth.

https://news.ycombinator.com/item?id=6923141

Look at this implementation: it's just a composition of a bunch of other libraries. no logic at all. This is how it should be: https://github.com/segmentio/myth/blob/master/index.js#L37-L...

secoif··on List of minimalist frameworks
@neiesc please make this a wiki instead of a readme. Edit wiki much more conducive to contribution than fork + PR + wait + hope
secoif··on JavaScript Promises: There and back again
not yet
secoif··on Monolithic Node.js
huh?
secoif··on Monolithic Node.js
This is the longest blog post I've ever read.
secoif··on Turn any application that uses stdin/stdout into a WebSocket server
https://github.com/maxogden/websocket-stream
secoif··on The Mozilla Developer Network has a New Face
Wow, it's very bright. Would be great if there was a toggle for a dark theme instead.
secoif··on UK Prime Minister: We have put in place Internet filters to block extremism
Internet filters are extremism.
secoif··on Why There Are No Women on Twitter’s Board, and So Few in Technology
Wow, this a perfect example of the dangerous thinking, the "facts", that got us to this point in the first place.
secoif··on An Attempt To Use Browserify
you can generate a gif with native js?
← PreviousPage 2 of 9Next →