sharpercoder

I can imagine a large SAAS provider can make heavy optimizations when data is marked immutable. In this case it seems to be a win, because humans want to have the data marked immutable.

Every time I see something about sqlite, I become sad. It reminds me of the failure of the w3 standards comittee to accept it as web standard. They rejected sqlite because no competing implementation existed. Furthermore, "public domain" license of the software was also a hurdle, iirc.

This is why I will actually do my first donation on KickStarter.

Just tried it out. Smooth sailing! A couple remarks: 1) It would be nice to explain some of the warnings. I had

    myFunction() {
        for (var x in xs) { .. }
        for (var x in xs2) { .. }
    }

it would complain about "Duplicate declaration of variable 'x'". Understandable, but then I'd like to know the javascript context information (apparently x is not in a sub-scope (as in most languages), but in the main function scope). 2) GitHub integration would be nice. A button when looking at source in GitHub which annotates the code with warnings would be quite an improvement over the current view.

How is stage polymorphism different then a language supporting embedded languages (e.g. javascript with regex)?

I remember a guy figuring out a fix for a specific motherboard. That type of motherboard suffered especially from these problems. The guy got a few hunderd of these, fixed around 95% of them and resold them.

I saw a documentary which analyzed footage found around 2000 iirc (discovered old footage) of the murder. The conclusion was that due to the wound exit, the shooter could never have been Oswald. It convinced me.

Who does the American public currently believe to be the shooter? Is there consensus for some theory?

I wonder about noise concerns. The concorde only reached supersonic flight on the ocean, not on land because of the sonic boom.

> 'We don't know what to do with it'

Is there a $1M prize for solving this problem?

How about syncing them at one physical place, moving while powered using a battery, then hot-deploy in target datacenter?

In the Netherlands, it goes as following:

- Car drivers' fault? -> Insurance of car driver pays

- Cyclist' fault?

1. Cyclist younger then 14? It's the car drivers' fault. In any case. Drivers should expect younger cyclists to behave unexpected.

2. Bicycle driver older then 14? 50% of damage is drivers' fault. Unless cyclist does reckless things the car driver cannot anticipate on (e.g. cycling through red traffic light over a busy intersection where drivers drive fast).

- Car driver & cyclist made mistakes? -> Cyclist is able to get more then 50% of damages depending on the situation.

I wonder if concentrated sludge can be collected and processed in a specialized plant with higher efficiency, reaching market efficiencies.

I really like the thumb-reach heatmaps. This has been my personal experience on larger phones as well: I should be able to "thumb the numbers".

I don't like a redesign because it's simply too ingrained. It's a sailed ship.

Note that our screens are big enough to waste space to nothing, at least for a phone dial screen. So we can redesign it to:

    ___________________________
    |                         |
    |                         |
    |                         |
    |                         |
    |                         |
    |                         |
    |                         |
    |                         |
    |                         |
    |                         |
    |                         |
    |                         |
    |        1    2    3      |
    |                         |
    |        4    5    6      |
    |                         |
    |        7    8    9      |
    |                         |
    |             0           |
    |                         |
    |_________________________|

Also interesting is that 2 centuries later, we're still trying to fight latency. Now with specialized wireless lines and shorter distance fiber, then with pigeons and couriers.

15FPS? Why on earth make that design decision? Isn't 30FPS nowadays considered substandard?

Have you considered accepting money on certain terms and subsequently using that money to do improvements? A couple millions can get quite far in improving certain aspects of the software, like UX, documentation etc.

It seems to me that your response was seemingly the right moral thing to do. However, I can also see a lot of practical benefits of having a pile of cash to improve open software.

The noise levels were great. I'm generally not very sensitive to it, but from what I remember is that I don't remember any noise leaks. Quite a difference from the 60's apartment complex I live in now, which has single-pour-concrete floors.

I lived as a student in one of these things [0] for 3 years. It had a small shower with toilet room, a kitchenette, electrical ariconditioning 9with heating), a large window on the head side and totaling ~21 square meter. For a student, this was just perfect. I only missed an indoor/safe bicycle storage solution.

[0]: http://www.ndsm.nl/en/location/tijdelijke-containerwoningen/

That was terrible UX. After searching for the link (why not place it at the top?) which can be done easier and clearer. I filled everything in, then it turned out the location was not supported. So I took the bigger city in the area. Then I got the message

> We don't support this location. Select a location from the dropdown menu.

There is no dropdown menu. I then hovered over the I icon, to only then learn my country is not supported.

I did it around 2008, I put it into a kitchen over with a laser temperature meter present to check temps. Basically, you remove the motherboard, strip as much as possible, put it into a controlled high temperature space (an oven), melt the solder and then let it cool down.

Had t40p for 10+ years. Dropped it from ~2m high several times. Got coffee over it numerous times. Kids of my sister left it drowning in a puddle of ice-cream ice.

I cleaned it with water a bunch of times, worked after drying. I even reflowed the motherboard after the housing got a little bit less stiff and random resets and freezes occured.

I think my sister still has it. I should get it back and hang it on the wall or something.

With all respect, leo looks like it is an editor from the 90's with its windows 95-looks. For me, that's mostly a sign that the developers do not adhere to modern development standards. As such, why would I invest time in using a dying product/project?

An addiction tries to replace a void in someone's life. Chances are big the environment of the addicted played a role in cerating the void.

Is bitumen a liquid or a solid? Technically, you can argue for either, but practically it seems to be very much a solid.

> The next big idea invariably seems to grow out of the next small idea;

Spot on and the key words here are "grow out". It seems that most Big Things simply slowly grow.

I thought this technique of eliminating dead code was called tree-shaking. And linking to be something entirely different: linking assemblies at (compile|run|analysis)-time.

Great video! Really enjoyed watching it. Great lighting. Towards the end, the images get flashy (don't do this please filmmakers, it makes my head hurt).

If the rails are solid state using for example magnetic levitation, I can see this being much cheaper to maintain.

Personally, I find distinguishing III and IIII quite hard in several fonts. However, the difference between [II and III] and [III and IV] is easier to read.

Imagine a driverless bicycle driving back to its base after being used byw the renter. A flywheel keeps its balance while stopped before traffic (lights), the electromotor thrusts it.