Skinney

48 ms·

451.
by Skinney 11y ago
> Simplicity would be to have a single mechanism for landing the Curiosity. Not 3. With one of them being a crane drop from a hovering rocket!? Why? Simple, in the way Rich Hickey advocates, means the opposite of complex, which means tha
452.
by Skinney 11y ago
If you need a generic component, then make a generic component. No one is forcing you to specify dependencies in all of your components.
453.
by Skinney 11y ago
I agree with this. The author should've mentioned enlive (you got a similar library that supports om) which allows html to be html, which should make designers happy.
454.
by Skinney 11y ago
Do you have any links that gives recent information about the JIT? Would be interesting to read more.
455.
by Skinney 11y ago
Reading this again make me realize that I'm wrong. Static typing will safeguard you against certain types of bugs that a dynamic language don't. The point I was trying to make was that a static language doesn't necessarily pr
456.
by Skinney 11y ago
> where did you get that idea? The core Go developers has said that an eventual implementation of generics won't arrive until Go 2.0, were they will allow breaking backward compatibility. That said, an eventual Go 2.0 release is pro
457.
by Skinney 11y ago
> Also you can send functions and code over the wire as well to run. Making some very interesting things that are just impossible to do in other languages. Well, you could do this in any language that has 'eval' really, which
458.
by Skinney 11y ago
I know you didn't, but if you have a language have a core semantic that only works "most of time," and "most of the time" is worse than "never," then you have a language that is worse than not having a lan
459.
by Skinney 11y ago
True, should have specified what I meant. The thing is, static typing doesn't necessarily protect you from more bugs than a dynamic language. For instance, Clojure is less prone to NPEs because you don't call methods on objects, a
460.
by Skinney 11y ago
By that logic, most object oriented languages like Java, C# and C++ are fundamentally flawed as calling a method only works most of the time. Besides, code in general only work most of the time. Static typing does not protect you from bugs.
461.
by Skinney 11y ago
Yeah. They are not really necessary in a Javascript VM that is optimized for these sort of languages anyway.
462.
by Skinney 11y ago
Probably based on personal experience. For me, whenever I start a project from scratch I usually start with the most dynamic environment I can find, then hack away until I have something that resembles the functionality I need, before locki
463.
by Skinney 11y ago
The keyword being "some". I've rarely had any problems with null/nil reference errors in Clojure, because nil is treated both as false and as the empty list, so most of the time you do the right thing in case of nil. You
464.
by Skinney 11y ago
For Clojure, I know there has been talk about this. Clojure allows you to insert Type Hints, which allows Clojure to remove reflection in certain cases, which improves both runtime and compile speed. Typed Clojure should be able to insert T
465.
by Skinney 11y ago
How do you know which feature will be merged last? In the teams I've worked in previously, everything happened in parallel. You had no way of knowing what feature was going to be merged when. So, essentially, we completed a feature-bra
466.
by Skinney 11y ago
Because features are not always isolated, sometimes they change behaviour based on changes in other branches. Testing features in isolation is different from testing an entire release.
467.
by Skinney 11y ago
Learning the Lisp syntax takes (quite literally) 2 minutes. Getting used to the Lisp syntax however...
468.
by Skinney 11y ago
Minor nitpick. BEAM doesn't have pattern matching built-in. Core Erlang does. Core Erlang compiles to BEAM bytecode with functions using regular if-statements. So basically: Erlang/Elixir -> Core Erlang -> BEAM. (Actually, I
469.
by Skinney 11y ago
As far as I know, you need to use rebase --interactive and delete the commit(s) that introduced the blobs. This will, however, create a new tree which can be painful for everyone involved.
470.
by Skinney 11y ago
The JRE is platform specific, the JAR isn't. Bundling them makes little sense.
471.
by Skinney 11y ago
For the same reason you don't deploy Windows, BSD and Mac OS X binaries of your Go program to a Linux server.
472.
by Skinney 11y ago
Setting memory parameters and tweaking them would be similar to deciding what compilation flags to use when compiling your program. I also much prefer profiling over JMX than re-compiling the application with the profile flag activated and
473.
by Skinney 11y ago
Depends. For me, creating an uberjar with my default project/package manager is easier than to setup cross-compilation with Go. YMMW.
474.
by Skinney 11y ago
No it shouldn't. `a` at the first console.log invocation IS undefined, so it is entirely correct.
475.
by Skinney 11y ago
A lot of people use transpilers like Babel or Traceur. They compile ES6 to ES5 (or lower) for use in older browsers.
476.
by Skinney 11y ago
Larger allocations causes the heap to fill up faster, causing garbage collection to happen more often (more traversing the graph). Also, a generational garbage collector like you have in Java will copy survivors to a new heap. The larger th
477.
by Skinney 11y ago
Why the downvote? The smaller the strings, the more strings you can allocate before triggering a garbage collection. Also, the smaller the objects, the less copying is needed when promoting survivors.
478.
by Skinney 11y ago
Reducing memory usage also reduces time spent in garbage collection.
479.
by Skinney 11y ago
Firefox did this recently, with great success. It's a simple solution that will reduce memory usage (and this, garbage collection). It makes perfect sense.
480.
by Skinney 11y ago
The reason I use Mercurial as an example is because that's the other DCVS I'm most familiar with. > A simple example of the usefulness is to be able to compare the behavior of different versions side-by-side (particularly when

More ›