vishbar

> There is an argument that Ruby is mostly LISP, so it could be said that lots of people use it very happily everyday.

How is that? I thought Lisp's "killer app" was its extremely powerful macroing system. Does Ruby have an equivalent?

I have what is probably a silly question. When you have an idea or something you want to mass-produce, what do you actually do? Is there some website that you can upload your design to, then receive quotes from factories that agree to manufacture N units at M dollars/unit? Or do you usually go through an agent?

Sorry if that seems dumb. I just have literally no experience in this area; if someone handed me a design and said "Manufacture 1,000 of these" I'd just stand around dumbfounded.

> Microsoft has been open-sourcing a lot lately, but it seems to be mostly "peripheral" software...

How is .NET Core peripheral software? If anything it enables developers with C# codebases to move away from Microsoft's commercial products.

Really interesting how it spikes on weekends! I wonder if this is because more home broadband connections are ipv6-enabled compared to businesses?

This seems more like a limited-lifetime side project rather than an actual viable startup. I've used MongoDB for situations like this where I just need to stuff some simple data into a datastore and retrieve it later without any particularly complicated queries.

Personally, if I were the author, I'd switch over to PostgreSQL the second I start worrying about more complex queries, though.

Well yeah, Node processes run a single thread (of user code). There's no concurrency there. Go and Java will use all available cores of the system.

A better (and likely more realistic) comparison would be to actually hit the database: node is async by nature so would better handle concurrent requests.

The "canonical" implementation of IDisposable includes a finalizer. As you said, that's the only time I've seen it used. Adding finalizers to classes has performance implications as well as the CLR will add any object with a finalizer to the finalizer queue (hence the GC.SuppressFinalize(this) you always see in implementations of IDisposable).

It was definitely an option for AIM, and I believe it was an optional plugin rather than a default feature. I remember freaking out friends in high school :-)

Go isn't just a threaded concurrency model, it uses an M:N greenthreads pattern. Also, when you say that Go I/O operations are blocking, it is true that they'll logically block a goroutine. However, under the hood, it uses the same libuv-style async IO (or IOCP on Windows) that Node does. An operating system thread doesn't get blocked; the goroutine is "shelved" and woken up again when the I/O is complete. It accomplishes the same kind of thing as Nodejs does, it just abstracts the async nature of the IO away from the programmer. I have to say I like it: procedural execution is easier to reason about.

It doesn't even implement IIntegerOperation!

True. Generating collisions is doable, but a.) and b.) are still huge constraints that make it orders of magnitude more difficult.

I'd imagine it would be nearly impossible to generate a collision that a.) does what you want, b.) is small enough to be unobtrusive, and c.) can be discovered in finite time with the computing power reasonably available to NSA/GCHQ/insert SIGINT organization of choice.

It seems like the "strategy" here would be 1.) submit a bid of $3000, and 2.) have a friend submit a bid at $1. The bidding closes, your friend intentionally sandbags the project, then you complete the project at $3k.

Noun-verbers are also really helpful for testability, not just refactoring. Using a decent mocking framework (or just rolling some custom mocks) I can test almost all my business logic through unit tests, reducing the time that tests need to execute and increasing their reliability

My bank, Capital One 360, has something like this. You can give a read-only access token to an external service and change/disable it at will.

This may be a silly question, but when it's said that these are not in a "stable orbit", what is the mechanism of decay? I'd imagine if they were in an elliptical orbit, they'd simply continue that way forever in a "perfect" system. I'd imagine tidal forces would be too weak and the satellites too small for them to have any effect.

Are they passing through the atmosphere and experiencing atmospheric drag?

That's probably the reason. Those are all rather niche markets.

Stick "ASP.NET MVC" in your resume or on your LinkedIn and you'll get swamped.

F# has a similar concept via the with statement. To use your example:

    type point = { x: int; y:int}
    let z = {x = 5; y = 10} 
    let y = {z with x = 17}