std_throwaway

I don't understand your question. Did you want to ask one of those?

* What is the difference between WhatsApp and Telegram?

* Which of both do you prefer for your personal use?

* For whom are those messengers suited?

This is a joke, right?

I suppose the error lies in statements like

"Everybody should eat X."

"Y is making you Z."

where the whole of the population is treated as one.

Yet, we are different. Our metabolic balances differ. Some persons lack certain genes needed to process certain substances. Other persons are super efficient at that and need more of some substances.

"One size fits all." does not work in nutrition!

People want Apple to be successful because they like(d) their products.

How is this problem solved for C++?

As xoa pointed out, it's very well suited for use as a persistent cache.

Couldn't you just uncompute instead of erasing to restore the ground state before computing something else?

To my understanding you just need energy to set the inputs, give it a little push and everything else runs on its own (forwards and backwards).

I don't like sensationalism as it clouds the mind with short-lived buzzes. Instead of always trying to alarm people of the big invisible terror lurking in the dark, we should educate people on how to handle the situation. What are the scenarios? What can we do ourselves for those scenarios (not to prevent, but to prepare)? Which cities and countries will be lost at what point in time? How do we protect ourselves?

Be constructive, be creative.

No, that would lead to paralysis.

Learn to live in a world where climate change is happening and adjust accordingly. There is no way going back now. The party is coming to an end. We must go forward.

You don't have to solve this problem in one day by yourself. You probably cannot really "solve" it at all. It's time to let go of things we cannot save and hold on to those which grow valuable in the future.

> MicroLED can be up to twice as efficient per lumen compared to OLED

Do you have sources for that?

To my knowledge, inorganic LEDs have the advantage now, but both technologies approach the same limits which means that in the long term both should deliver the same efficiency. In the long run I don't see a deciding difference here.

One major complication for OLEDs is processing and sealing because they tend to have a short lifetime for various reasons. This sounds simple but in practice it makes everything much more complicated.

I don't like opinionated pieces like the one presented here because while they are right about some things they miss other things and present half-truths as full-truths.

In my experience (and I have little of that) it's important to know the upgrade path and adjust your planning accordingly.

How many users can you serve with your solution?

How big do you expect the market to be in that stage?

What technology would be the next step?

How do you get there? How much more work would it be?

Always be one step ahead with technology, but not two. Most markets are surprisingly small. Most use cases scale surprisingly well. You can probably push your solution by an order of one magnitude if you need it quickly.

In order to answer the questions you need people who know the product, the (potential) technologies and the market. When you start you probably won't know any of that. See the first prototype you deploy to the customers as a means of collecting data for the first production version. Your first product is not your first product. Your funding should respect that. Get it done quickly with the aim of answering the critical questions. Then go back and design the next version "good-enough" for the second scaling step with the upgrade path in mind.

"Why Kids Shouldn't Sit Still outside of Class"

Suppose there's two doors. You can't decide. The host opens one. There is no goat behind that one. Now you know for certain.

But how do they get the light out? Mode density in air is only about half of what it is in organics.

Title doesn't do any justice, it's an all-discrete circuit made from diodes, transistors and such. They are soldered not on a PCB but mostly free hanging in air above a copper ground plate. One wrong move and "bazoing" sparkles. The guy didn't draw a schematic beforehand either. He mostly made it up as he went. Amazing.

http://www.eevblog.com/forum/projects/oscilloscope-pong-for-...

It's about half and half, 50x comes from the language and 50x comes from experience. The important part is to add those factors together by good management.

He picks it up and adds one tiny modification (changing endianess). Others might need to change another detail making their version incompatible again.

Oh no, there are 40 competing standards. We must make one to unify them all! Oh no, there are 41 competing standards.

People should not use a non-compliant file system driver to create corrupted entries. NTFS mounts are for windows machines only.

I don't think this is true. Phones are still getting bigger and thinner while battery life only decreases slightly. This game can be played indefinitely.

At first glance, the status page of btrfs look horrible:

https://btrfs.wiki.kernel.org/index.php/Status

The problem areas are mostly RAID and exotic features. RAID can be handled by a different layer and most users don't really need the exotic features.

Judging from the media silence in the last months I'd say either people stopped using btrfs or it just about works good enough for everbody.

It looks like it takes quite some time till it is fully implemented. Why should we start using it right now instead of btrfs/zfs?

Don't loop around waist if other people might pull on your side. And don't even think about making a knot.

For groundbreaking technology, 20 years is shorter than you think.

It could take 5 years at university to get it working at all, 5 years as a startup to get the first product to market, 5 years to scale up the marked from zero. Then you only have 5 years left where you actually have a chance to make money.

Shortening the patent life to even 10 years would make it unattractive to patent groundbreaking technology.

If you immediately make it to market, the story is different. In the software-sector everything is moving much much faster than in the physical world. The negative effects of patents become much more obvious then.

One way to go about that is to limit the license fees the patent holder can get. This would change the game in major ways (mostly for the better I think).

I come from the angle of "absolute beginner" who is trying to get started quickly. If you are really "looking to put things into production" you might be right. Using those boards I proposed will always have big disadvantages.

The original article is not written for absolute beginners, but for people who would go through the pain of soldering 100 pins to a self-designed PCB and failing 5 times before getting a working version.

That depends on what the product may cost and how many you intend to sell. In general you might be right. But if you look in getting started and having a solution (suboptimal but working) quickly, then they are a good choice. Maybe not the best choice, but good.

Of course, do they come with a nice IDE and a big library/ecosystem of soft/hardware examples?

As the other poster stated, you don't really disagree, just misunderstand.

You can actually do everything you need in the Arduino IDE and then leave the IDE, compile and upload your own program written from scratch to the UNO. All that while staying compatible to the dozens of hardware extensions out there.

The "Arduino" part is not the destination, it's three quarters of the path to the destination and that path is already paved.

You can actually do a soft transition from the (opaque) Arduino programming style to a programming style closer to hardware. After all, Arduino programs are just C++ and you can plug in your own functions and assembler and you can even compile and upload your own ASM/C/C++ program written from scratch and compiled with the gnu-avr-toolchain to the UNO.

After you have done all of that it might be a good idea to start soldering the AVR on your own boards.

I'll have to look into those. Being able to start with the Arduino IDE is a big plus for beginners.