beders

52 ms·

601.
by beders 10y ago
No shit, sherlock. Germany: 200MBit for 24 euros/month
602.
by beders 10y ago
No mention of Kontena.io ? Too new or too European?
603.
by beders 10y ago
It is a stupid, broad statement without proper context. It really depends on what your project is, what your goals for maintainability are and what programming language you use. Two things about testing: - test to confirm your spec - if you
604.
by beders 10y ago
and then you press backspace and you are back in hackernews!
605.
by beders 10y ago
It's the same old problem. Writing as little code as possible is a non-goal for a team of developers. Writing maintainable, easy-to-understand code is much much more important. And while I value Lisp (I started on Allegro Common Lisp o
606.
by beders 10y ago
It's all about the read. But a different one. The human ability to read code. You can write very dense code in Lisp (and the author makes the point several times on how little lines of code you need for this vs. that). However, who&#x2
607.
by beders 10y ago
It is not a Zero sum game. The moment you actually need to maintain a large codebase for years, strongly typed languages are much more cost-efficient. Finding out, with absolute certainty, which code calls which code under which circumstanc
608.
by beders 10y ago
Thanks! I'll give it a try.
609.
by beders 10y ago
Very cool! I'm wondering if it will work on Nashorn. I actually have a need to be able to debug JavaScript code running inside Nashorn without touching the JVM debugger.
610.
by beders 10y ago
Build faster browsers. Don't be afraid of dogma. There were times before there was a DOM (you might not have been born yet) and there can be times after DOM :)
611.
by beders 10y ago
Vert.x basically gives you everything that node.js has - and it spins up several event loops, making your code scale without having to run several node processes. It also allows you to mix in worker threads that are allowed to block (for I
612.
by beders 10y ago
It's all about cost. If they would switch to more efficient languages, they could probably run on half of their current servers. But there's the huge cost of rewriting something you already have. Will that affect your total cost
613.
by beders 10y ago
You seem to enjoy switching tools and methodologies and see it as part of embracing Node.js. Others don't have that luxury and just can't afford that. And if your software needs to be around for more than 5 years, you want to keep
614.
by beders 10y ago
I'm mostly lamenting the overall lack of progress in creating reliable, bug-free software. You would never let a software engineer build a house, would you? For some reason, the discipline of architecting and building houses is far mor
615.
by beders 10y ago
Did you read what I wrote? I already said that you need a disciplined team. Good luck keeping that team together for years to come. Not sure if you are disputing the fact that keeping code around is a challenge, or not.
616.
by beders 10y ago
If your IDE is your runtime environment. Sure. I've started with Allegro Common Lisp, so i kinda know a thing or two about that. The success of Smalltalk then speaks for itself?
617.
by beders 10y ago
I think I didn't express myself correctly. Younger engineers are ignoring lessons learned and are thus forced to learn them again :)
618.
by beders 10y ago
if all the libraries you are using are as well...maybe.
619.
by beders 10y ago
And someone needs to pay for the overhead of 'community fixing itself'. And the Promise/A+ spec is so bare-bones, it is laughable. And the actual issue is that not every module is embracing it yet. Sure, it will all be fixed.
620.
by beders 10y ago
Now all of a sudden, having types and some standards to gather around doesn't sound like a bad idea anymore ;) I agree with one of the commenters: Lessons already learned by older engineers (who went through similar woes with other lan
621.
by beders 11y ago
Comparing a web framework with a JVM language is completely pointless. A better comparison would have been: Vert.x vs. Node.js
622.
by beders 11y ago
The author might like RiotJS instead.
623.
by beders 11y ago
Listen to an old man that has gotten his feet wet with Allegro Common Lisp back in the day: Avoid macros if at all possible. Use functions if you can. Special forms that don't follow the standard evaluation rules are putting additional
624.
by beders 11y ago
if you put s =: ({. , }. /: 12"_ o. }. - {.) @ /:~ in my code base, you are going to get smacked. Expressability of programming languages has a cognitive limit and J is flirting with it.
625.
by beders 12y ago
If you are mapping your RPC-style API into a REST interface, you are doing it wrong. REST as an architectural style wants you to think as your API as a collection of resource representations that can be manipulated through simple verbs (a
626.
by beders 12y ago
This!
627.
by beders 12y ago
Has anyone spotted a buildpack for Heroku?
628.
by beders 12y ago
"These ideas were initially worked out in the 1970s and 80s, and, in the 90s, were carried up by a huge wave of hype—the object-oriented programming revolution. Suddenly, there was a large tribe of people declaring that objects were th
629.
So you are having trouble with Webstart on Java 7u51?(sososoftware.blogspot.com)
4 points by beders 13y ago|0 comments
630.
by beders 13y ago
And here's a completion code that works for Mac OS: function _jump { local cur=${COMP_WORDS[COMP_CWORD]} local marks=$(find $MARKPATH -type l | awk -F '/' '{print $NF}') COMPREPLY=($(compg

More ›