larschdk

They had bingo games running on Teletext in Denmark.

There were also interactive pages where you could phone in and press numbers to access a much larger set of information. You'd get your own temporary page number (that anyone could technically see), and the teletext broadcast equipment would insert your updated page into the stream when you pressed a number.

I thought this would be about optimizing or tuning SQLite settings, but it's about query and schema optimization.

Arguably, it doesn't. New features can be necessary to stay competitive, such as the Vector API to utilize vector instructions.

You don't know that they do. They did redirect when you tested, but they may not for everyone. They could easily selectively download-snipe anyone they have identified by IP address or even regional. Big security threat.

Detecting a security issue is one thing. Detecting a malicious payload is something completely different. The latter has intent to exploit and must be addressed immediately. The former has at least some chance of noone knowing about it.

GIMP is my pet-peeve as well. I literally have to "read" each icon to find the one I'm looking for. Luckily you can change back to the color set, which is a lot better, although not perfect.

Such an effective design. I immediately recognize even subtle difference between icons at the lowest sizes. Meanwhile, today I get lost on my Android phone and in most desktop applications with low-contrast and monochrome icons.

France has a civil law system where precendent is not binding nor persuasive.

That's not even satire!

Scientific discoveries are not instant, but build upon earlier work.

* 1824 - effect proposed (Joseph Fourier)

* 1827/1838 - further evidence (Claude Pouillet)

* 1856 - Speculation that a high vapor atmosphere would give a warm planet (Eunice Newton Foote)

* 1859 - Demonstration that hydrocarbons had a significant effect (John Tyndall)

* 1896 - Quantification of the effect and prediction of global warming (Svante Arrhenius)

* 1901 - Greenhouse name used (Nils Gustaf Ekholm)

The greenhouse effect in itself is critically important in maintaining a liveable temperature on Earth. It's a runaway greenhouse effect causing global warming that is the problem. Anything before 1896 was about understand the basic effect, while after we began understanding that we were affecting the system by emitting gases.

You aren't looking carefully enough. I find so many inconsistencies in these examples. Perspectives that are completely wrong when the camera rotates. Windows that shift perspective, patios that are suddenly deep/shallow. Shadows that appear/disappear as the camera shifts. In other examples; paths, objects, people suddenly appearing or disappearing out of nowhere. A stone turning into a person. A horse that suddenly has a second head, then becomes a separate horse with only two legs.

It is impressive at a glance, but if you pay attention, it is more like dreaming than realism (images conjured out of other images, without attention to long term temporal, spatial, and causal consistency). I'm hardly more impressed that Google's deep dream, which is 10 years old.

I don't find this music to be good in any way. It sounds interesting over a few notes, but then completely fails to find any kind of progression that goes anywhere interesting, never iterating on the theme, never teasing you with subtle or surprising variation over a core theme, no built-ups or clear resolution. Very annoying to actually listen to.

My first discovery was "Santauron"!? - by combining Santa Claus and Sauron.

They have already taken outside investments in previous rounds. This is the Raspberry Pi Ltd (formerly Raspberry Pi Trading Ltd). The Raspberry Pi Foundation is still a charity.

To clarify, this is Raspberry Pi Ltd (formerly Raspberry Pi Trading Ltd), a subsidiary of the Raspberry Pi Foundation (the charity).

I'm curious how this will affect the foundation's mission, but I guess they are already affected by the outside investments from previous fundraising rounds.

The code effectively flashes the monitor at 30 Hz on any 60 Hz monitor (the time delta will always be 16.66 ms or more). I have tried this before and noticed a lasting effect on the monitor that was visible after stopping the flashing. Just a warning. I thought I had damaged the screen.

The LGPL license doesn't work that way. The rights that it establishes follows every time you transfer the work between legal entities. If I transfer the work to you, I need to extend the rights granted in the license to you. I can't expect others to do it for me.

Very different. They can do that, because they are in control of the components and build process. That's much harder for someone else's deliverables.

My guess; Unity doesn't want LGPL code in component they re-distribute, because the responsibility to comply with the license requirements falls on them, since they are the ones redistributing. It's not that they can't, but they wont take that responsibility, which is understandable. They would basically need to audit every component to ensure that the end user can build and replace LGPL parts with their own.

It's not impossible to comply with LGPL under the app store model, but the responsibility falls on the distributor, which is Unity in this case. I can understand that that is something they are not able or willing to do. This doesn't mean that they can't comply with LGPL for components included in Unity itself. I don't see any double standard here.

Related: Grey Hack is a fake OS, Network, Internet in a multiplayer game where the objective is to hack (including each other). It simulates many basic functions quite well (you can steal files, place files on other computers, install software, run commands from a command line, including imitations of many tools). You can also write your own programs.

Revenue per employee is never a goal in itself. Only revenue, expenses, and strategic goals. If they can meet their strategic goals with less resources, they over-hired.

In my case, wireless SoC chips (BT, BLE, DECT). Current generation are ARM M0 cores, but 16-bit RISC/CR16 architectures are widespread still. Not expecting language to provide platform support, but SoC providers don't either. They provide C frameworks only, if anything.

Not easily portable to most microcontroller targets: No SDK for our target SoCs and official SoC/µC support. Increased code size (which is also a performance issue in many SoCs). High cost of retraining engineers. High cost of reenginering existing code base and tooling. Lack of commercial support.

I'm optimistic about Rust, and it taken great strides to replace C, but there are still many hurdles that prevent it replacing C in microcontrollers and SoCs. Even if it wasn't for the lack of a platform SDK and porting existing code, the risk is too great with lack of official support for many commercial SoCs.

You troll, but I'll feed you. There is no universally better language for portable high-performance system programming for resource constrained platforms. Every single alternative have unacceptable trade-offs.

I wish it had a less click-baity name than "transparent wood". It's wood with the lignin replaced with resin through a chemical process. Of course things can be be transparent if you replace them with something else, but then they are no longer wood if you remove the wood! It's not the the wood that is transparent, it's the resin! Dammit.

I tried your code on prettier.io and got a result that was more visually consistent than what you pasted here.

I'm paranoid after enabling 2FA after failing once to save the recovery codes correctly. Not sure what actually happened exactly, but when I managed to get back in despite odds, the shown recovery codes were _different_ from the ones i had saved locally.

Losing your authenticator and recovery codes means the account is lost permanently. This feels like a bigger threat to my account security than not having 2FA. Not saying it _is_ a bigger threat, but it feels like a bigger threat.

Same here. If you flick the sun light on and off, much of the surface shifts several pixels.

What is the use case for a mutable environment past initialization?

It seems like a complicated and error prone thing to be using no matter if it is thread safe or not. You can set up your own environment before you launch threads, and you can launch child processes with a different environment from the current process without modifying your own. If you fork, you can modify the environment in the child without affecting the parent until you exec.

And even setenv() if it was reentrant and couldn't cause crashes, it wouldn't be thread safe, since threads share the environment and could get their environment changed under their feet.