iends

54 ms·

211.
by iends 9y ago
Business insider says 37 minutes from North Korea to Honolulu. I imagine it’s only a few seconds difference between the various Hawaiian islands. However, you don’t really know how quickly the alert goes out. Do you estimate you’ll have mor
212.
by iends 9y ago
Are entrepreneurs that are starting their business really a niche that pays well? Seems like it wouldn't be. Seems like you get either "build me the next facebook for $500" or a lot of small business with a total budget of $5
213.
by iends 9y ago
I am a full time employee currently, but have done consulting on the side for $50-$100/hr several times. I've never tried to negotiate weekly rates because I've only been able to do ~10 hours of work a week on top of my full
214.
by iends 9y ago
One of the problems I've always had with patio11's advice is that the skills he brought to a job was something that could easily be measured, e.g. he mainly did sales funnel optimization so it was easy to see the before and after
215.
by iends 9y ago
Sails had a bad reputation in a lot of NodeJS circles. Most people use express/koa and use knex or pg-promise.
216.
by iends 9y ago
Sadly CoffeeScript 2 recently came out, so not dead...but the ecosystem has moved on.
217.
by iends 9y ago
GopherCon in the USA is always great if you have any interest in Go.
218.
by iends 9y ago
I always hear reInvent is terrible because the crowds and things inevitably go wrong at that scale.
219.
by iends 9y ago
I often don’t understand the Go teams obsession with compile times, but I’ve never worked on large Java or C++ code based that take forever to compile. I mostly want them to optimize for runtime performance even at the expense of compile ti
220.
by iends 9y ago
node —-inspect is a great debugger but last I looked the tooling around memory wasn’t very good. As far as I know, the best practice is to use Ben Nooordius’ heapdump tool (which is super flakey between bugs and Linux oom killer) or lldb wi
221.
by iends 9y ago
I guess you’re talking about well published changes resulting in new major versions being released?
222.
by iends 9y ago
I’m specifically talking about things not under the Go 1.0 compatibility guarantee because those things are obviously reverted. Different Go packages from the Go team have different guarantees, for example being compatible with the with the
223.
by iends 9y ago
I think a lot of the differences between how people view Go is based on where they are previously coming from. The C/C++ folks are used to worse or more complex type systems so they view Go as fresh air. The “better python” people love
224.
by iends 9y ago
This is the only article I'm aware of that has comparisons between a number of languages/platforms: https://hashrocket.com/blog/posts/websocket-shootout
225.
by iends 9y ago
There was an event loop implemented in Go on HN a few weeks/months ago that people might find interesting: https://github.com/tidwall/evio
226.
by iends 9y ago
It being implemented incorrectly is not a property of the Go language, though.
227.
by iends 9y ago
You're comparing core libraries of Go with non-core libraries of Node.js. Since Go libraries are not versioned without a tool like dep, you're putting trust that master doesn't have breaking changes vs hoping the maintainer f
228.
by iends 9y ago
Channels have a performance overhead over handling the locking yourself. Maybe look at stuff from Tyler Treat to learn more (maybe his most recent talk? https://www.youtube.com/watch?v=DJ4d_PZ6Gns ) but there are some other
229.
by iends 9y ago
It's incredibly easy to throw stuff together in Node.js, it's much harder to maintain over time. TS helps with this but you still run into really hard to diagnose memory leaks (mostly in 3rd party packages written in C++, but some
230.
by iends 9y ago
Hopefully it's linear, or it's implemented wrong.
231.
by iends 9y ago
This is not considered idiomatic Go and would be a premature optimization unless you ran a profiler and determined that channels are actually your bottleneck. It sounds like this has not been done.
232.
by iends 9y ago
Some random thoughts as somebody who codes a lot of Node.js at work and a lot Go in my freetime (and sometimes at work): Did you try using pprof and the other tooling go provides to better understand your performance limitations? Tooling is
233.
by iends 9y ago
(Not the OP) That's the problem, I see the following often suggested instead of Go: Java - maybe if you use Spring Boot you can get around some of the boilerplate, but there is a ton of baggage in the ecosystem. Clojure - This is reall
234.
by iends 9y ago
Currently product managers and some dev leads are currently working with our legal teams to build requirement epics around GDPR to be worked on very early next year by development teams. About a year ago we had a big push to be fully HIPAA
235.
by iends 9y ago
The most painful parts of the Go ecosystem are directly tied to the fact that the Google is making Go for themselves first and foremost and the community is an afterthought.
236.
by iends 9y ago
.07% interest is kinda low. You can get 1% or better these days with some banks/credit unions.
237.
by iends 9y ago
I'm sure paying with a stolen credit card is no problem for somebody willing to steal your identity in the first place...
238.
by iends 9y ago
Long after it matters to me.
239.
by iends 9y ago
That model is clearly not working currently.
240.
by iends 9y ago
Enjoying those fees?

More ›