djfm

they have no doubt been doing it, they're just using the panic of a brainwashed population thinking they're on the brink of Islamic revolution to normalize it

Random audits in data brokers' data centers?

Software on consumers' devices that records ads seen and file complaints if consumers are still being tracked? It's very easy to detect algorithmically that you're being shown personalized ads.

This should be open-sourced so that the probability of creating a dangerous true AI is lower. I fear there may be something very wrong in this but I'd love a DIY grow-your-brain kit with a USB interface to experiment with. This machine would have an awesome "hello, world" program.

I was gonna comment the same, so thanks for getting all the downvotes :)I think it's not that sexist but at first I was shocked. Now I think it is just using way too many stereotypes in one sentence. I think they realized it was sexist but thought "but we're the BBC, they will know we don't mean it like that" (which is probably true).

Isn't the title a bit misleading?

Hence, our attempt to convert high-level code to assembly code takes us one step closer to completing the dream of making a chemical compiler.

I would add mindfulness meditation to the list.

As a developer I don't estimate work based on number of lines I expect to write, so while this metric is interesting I do not think it explains why we miss deadlines. It does indeed show that things usually are more complicated than we think. But with that knowledge, I'm pretty sure I'll keep missing deadlines.

Also, commenters to this thread won't be let through.

No offense taken.

I said I like to write it this way, not that I always do it.

why code like that

It's a fun exercise.

it would be a huge waste of time and energy

I don't fully agree on this: from the name and signature it's pretty clear what the function does, so you don't need to waste time "parsing" the details. And with unit tests it is also very low-risk.

But that's speculative, in a real project I'd just use lodash.

Shouldn't it be ".map(([prop, value]) => ...)" ?

I like to write it this way, using as much syntax sugar as possible:

const mapObject = fn => obj => Object.assign( ...Object.entries(obj).map( ([key, value]) => ({ [key]: fn(value) }) ) );

it's very unlikely this is going to be the bottleneck in your application

My thoughts exactly!

The amount of things you need to know in order to use react and redux is ridiculously low.

You're basically just composing functions of two types "(state, action) => state" , and "state" => html.

The boilerplate consists of a few functions (really mostly createStore and connect) that are incredibly well documented.

There's almost nothing to understand and redux itself is almost not a lib (only 318 LOC). The whole thing is a pattern and redux is just a small, very well written key component of the pattern.

When people debate redux they debate about programming, not about a tool. That's why it's interesting and why it will never end.

Well "a.b.c" violates the principle that you should never access a property more than one level deep anyway ;)

But in this case it's pretty straightforward to write a function like "get('b', 'c')(a)" or use a lib like lodash [1]

[1] https://lodash.com/docs/#get

Right. We might as well just compile our JS to Java.

Instead of using web tech to build native apps I think we should focus on improving browsers so that web apps behave more like native apps and have the same capabilities. Browsers should be the cross-platform VM and webassembly is a good step in that direction.

Yeah, technology loves cycles.

"Hey, let's write an editor for a browser. Oh wait, we need a browser for that editor".

Something good will probably come out of this eventually. I mean if they manage to turn electron into a true native cross platform app framework it's nice.

This is interesting, I love writing this kind of frameworks myself to get a better understanding of the ones I use in production.

But I fail to see which problem this tries to solve or which novel solution it illustrates. It looks a lot like React without JSX (which is not bad).

I don't understand what they mean by 11 dimensions. Last I checked we only have 3 spacial dimensions (exotic theories notwithstanding).

And no hoverboards, damn!

The title is misleading, I thought this was going to be about "True AI". The AI doesn't write its own code, it writes code instead of you but always uses the same code. Or did I misunderstand?

Surely some folks will re-implement it :)

I for one am willing to contribute the day wayland becomes too mainstream.

Hallelujah the [1]missing dropdowns are fixed!

Long live the best WM ever!

[1] https://github.com/xmonad/xmonad/issues/42

I try those new shiny DEs from time to time and always come back to xmonad.

In particular, I need to be able to have desktop #x on display #y and desktop #z on display #t, i.e. have virtual desktops independent from the multiple displays setup - a feature that other DEs / WMs seem to never provide.

This is very practical to, say, keep your emails always visible on one display while switching between other tasks on other displays.

Sure, sometimes a release of xmonad will make the chrome dropdown menus stop working [1], or some other weirdness, but all in all, it's quite stable and I can focus on creating a workflow that really suits me and that I never need learn again.

[1] https://github.com/xmonad/xmonad/issues/42

At least the name is great. I think it's reason enough to install it.

Yeah, can it really do both properly?

It's probably harder than we think because of the scale of it.

I have mixed feelings about twitter. On the one hand I see it as a nice way to make interesting conversations surface and reach a wide audience. On the other hand I see it as a constant stream of ads. I don't know if I'd be happy if it all goes down, or if something better comes along. Which problem is twitter actually trying to solve?

Totally agree. I see programming as a way to run experiments on your very ability to reason about things. Or on the thing inside you that has reason. I believe much of the positive side effects of programming come from this.

I'm French, I'm not always proud of my country, but today I am!

I'm fortunate not to know anyone with HIV, but this news truly brightens my day.

At our company developers rarely write tests. They rely on the QA for testing. Obviously it doesn't work, like, at all. I think a key aspect of this post is to highlight the fact that testing is in fine the developers' responsibility. Test engineers are here to make it easier for them to write tests.