176 karma · joined November 27, 2014
- It's hard to figure out what the dependency graph looks like just from promises
- That pattern is verbose and results in gross types when you do it in Java
- With this library, you can easily profile parts of the algorithm to see what's going slow, what's taking a bunch of memory, etc.
Depleted Uranium and the stuff that comes out of depleted uranium (which I think would account for most of the spent fuel in the United States) emits beta and even shorter alpha radiation. Does that mean that the concept could work with depleted uranium?
How does this work without cloning vast swaths of code and saying:
if (feature)
loadModuleA();
else:
loadModuleB();http://www.delek-group.com/Holdings/EnergyInfrastructure/Del...
Where does bytecode manipulation or code generation happen in Dropwizard? Reflection for sure, but not any more so than any major web framework in a dynamically typed language.
Maybe you're referring to the SQL library they suggest (which I've admittedly never used heavily). But I don't see how you can have a SQL library without generating SQL.
An analogue for rust would be something that detects the platform at runtime and then downloads a statically linked (?) binary that works on that platform. It can also exploit the ivy cache as the Scala compiler is just a library as far as SBT is concerned.
Isn't that a deal breaker? I would assume that downloading and checking in the binary for a whole compiler for 3+ platforms is untenable.
It's not so black and white though. There's plenty of difficulty in keeping a mono-CI system running and being helpful.
* The CI service becomes a single point of failure for all developer productivity
* Running a full build on every commit while accounting for semantic merge issues (so serially) is non trivial.
Jane Street did a pretty good write up of how hard this can be: https://blogs.janestreet.com/making-never-break-the-build-sc...
Sure, companies aren't dropping existing code in Scala, but I would be surprised if large organization were to push for new code to be written in Scala instead of Java 8.
Edit: link
Most carriers allow you to blacklist phone numbers (although that very well may not have been the case when those laws were written).
Isn't the solution for npm to have tighter controls on where it will download packages from?
It sounds like it's basically a BTree that stops branching at a certain threshold, but I'm almost certainly wrong.
http://www.theatlantic.com/magazine/archive/2014/12/the-shaz...
My biggest gripe with this notation is that it assumes you're playing in a key, so the lines go <D E F# G...> for the key of D. That causes the spacing for a D chord and an E chord to look different, even though they're composed of the same intervals.