kagia

Oddly specific numbers, 50k records take 5minutes?

What was the authors methodology?

I just started working through Google's free course. Tomorrow I'm posting about my day one experience here: https://kagia.github.io/2018/12/29/learning-machine-learning...

As it says on the linked post I'm not learning just for knowledge sake but I very much intend to apply what I learn.

You can run it locally for development. Just look for dynamodb-local images on the docker hub.

Just a warning, parts of that page may be disturbing and or distressing to some. The references to animal testing are particularly gruesome (to me anyway).

I feel that typescript being only 2.0, should be in a position to break things once in a while.

If you pay too much attention to keeping legacy code 'alive' you end up complicating matters with either compiler-flags all over the place or redundant API's i.e win32 api (old+new+newer versions of the same function).

If 12megapixels can produce 10 to the power 86696638 images, and we came up with a way of enumerating those images, could we then build a function that given anyone of those images return the index of that image within reasonable time with current hardware. ie. "you have just taken 3999999987493th image"?

This article should be taken with a good pinch of salt. It seems to be more speculation than anything else...

If only it were April fools...

If the author is around, How long did this take? It's slick, but what impresses me most is when I customize the interior from the inside view.

Well done!

It worked really well for me, and I hope to see some more demos!

One place I can see this really shining is as part of a script that generates fixtures for Django apps.

I'm not sure a 'readable' preemptive micro optimization is any more sensible. I think we should limit 'sensible' to preemptive macro and architectural optimization. A programmer should examine what their compiler is spitting out before they decide they can do better.

>A programmer should not even try to optimize the code that is not proven to be a bottleneck by carefully profiling the whole program

All who haven't taken note, please do!

I doubt everyone agrees to that coding style, I certainly don't. However when submitting code to a project I'd still stick to the prescribed coding style, because I believe consistency in any code base can be just as important as any other measure of readability.

not really. there is nothing wrong with overlapping, and most tiling WM'S are user managed in some way.

>not a swipe at you at all

no problem! :)

I like the fact that they are being cautious about using the term hate speech. It has become a catch-all for anything that's unpleasant, even if harmless to society.

If anyone wanted a background I found this link: http://voicesthatpoison.org/guidelines/

Totally agree with you!

The problem though is getting rid of the desktop would not go down well with the majority. you'd need a way of proving that you can still make multi tasking painless. Currently a desktop environment means I can resize and arrange windows to allow me to work with multiple apps.

One idea is have some sort intelligent system for deciding how much screen real estate is needed for each app and how they can be grouped and arranged into sensible workspaces.

I for one think it's time we saw bold and ambitious attempts at changing the desktop.

Most desktops today are arguably variations of the desktops we were introduced to in windows95 and OSX (v10). The colours, placement and names change but rarely does anything new show up (save for metro desktop).

With wayland and mutter/qt+ this is a great time to try out wild and out-there concepts. It's the only way to break out and really change the desktop.

I can understand peoples frustration; the desktop, after all, wraps up everything we experience when we use our machines. However I will approach this with an open mind, and I certainly hope others will do the same.