donlzx

I like the Odin language because it is really joyful to programming with it. Hope there are more resources and mature packages besides gaming development.

AFAIK, the digital interface of the physical layer (PHY) of the Ethernet stack are pretty much standardized (MII/RMII/GMII/RGMII). Most SOCs implement their own MAC layer, but are usually compatible with off-the-shelf PHY chips. The function and interface differences in proprietary MAC implementation is where the complexity of the kernel driver comes from.

Suppose that we also standardized the interface between the MAC layer and the kernel and add an FPGA inside the existing PHY chip which is opened to real-time programming, a ton of optimization can be done. For example, DDOS packets could be thrown away well before reaching the kernel space.

Previously I had done that with some low-cost FPGA kits, with less than 1K of HDL codes, it could get out only the IP packets wanted and then pass the packets directly to the application layer via the memory interface between the embedded CPU and FPGA logics.

I think a programmable network interface is well worth the money if we care enough for openness and efficiency.

This scenario scare the hell out of me. Is injecting/intercepting brain signals directly really the way forward? Do we really want to create monster human species?

IMHO, future AI should be used to enhance human cognitives in a noninvasive way. Never in such a dystopian way as in the movie "The Matrix".

Co-founders or not, the underlining reasons are alike for people (entities) with different personalities (characteristics) working together.

Only one person in charge will always do, if he or she has a very strong personality and also has appropriate supporting subordinates.

Two person founding team will be great if their personalities are complementary, thus one plus one is bigger than two. There are many very successful enterprises in this group, such as Apple, HP, etc.

In initial phases of founding companies, projects, etc., always avoid groups of three strong personalities at all costs. Trinity is a very special case that will ensure endless internal fighting/competition, low efficiency and sustained tensions. However, trinity is good for long lasting (market) competition and ensuring all parties will not be easily wiped out. Example cases: a) US-Russia-China relations; b) President-Congress-Senate structure. c) Firefox-Chrome-Edge browsers;

For groups bigger than three, if the number of prominent members with strong personalities is less than four, see previous cases. Otherwise, avoid at all costs.

I actually think AlphaGo is a perfect example of Human-machine cooperation. Deep neural network is the easier part, the intuition and architecture design by Humans are the most critical part.

Why not patch against the latest stable version?

After the IEEE $25 monthly service came out, I subscribed for three years until finally canceled it. Honestly most of the papers I downloaded were junks, the only reason I download them was to verify the available references.

The paper quality declination plus publication quantity inflation are the main reasons in this "Sci-Hub" crisis.

I think this is a bad idea. Now imaging a new channel for all sorts of fake BSODs and out-of-band malicious links in the shown QR codes.

Kudos to the ReactOS team. I've tried the 0.3.x release about ten years ago and was a little disappointed. However, after a decade I've got a new perspective to appreciate their work.

I've kept several of my used laptops (Toshiba Satellite laptop, IBM Thinkpads, Lenovo Thinkpads, etc.) mainly for commemorative purpose. However, they can still boot and works fine with outdated OS's and extinct software. A potential very good use of them is to open my old archived documents, but I'd rather not to mess with these fragile machines.

When I checked my old archives, usually only plain texts and JPEG photos files are fine with current OS's and softwares. Nealy all my old software projects (mostly with Visual C++) no longer compile or run, or missing dependencies (DLLs, component libraries, tools, etc.). Even though I've backup most of the tools I used at that time, most of them would be a huge pain or impossible to reinstall correctly with right system dependencies.

Therefore I've come to think that the only meaningful archives are data with executables, i.e, documents with related spec, contemporary software and OS. In this aspect, a good Internet archive methodology should be like this: 1) data; 2) Fully installed and working software packages; 3) Running free OS such as Linux and ReactOS; 4) OS emulator on available hardware such as Virtualbox and KVM.

The importance of ReactOS here is that we will have a working OS on modern emulator or hardware for archiving purpose.

I'm omitting the hardware platform here, but it should be the other important aspect of archiving our knowledges.

So, Jessica is the Socrates for YC, and YC is the Socrates for YC start-ups.

Successful founders are usually doers that often make bold adventures and can execute plans efficiently and ruthlessly, but they need consultant guidance from a wise person. I guess this is the YC's success formula?

I hope the idea of progressive downloading partials can be applied to other files types as well.

For example, if commonly used libraries such as minified Javascript source files are encoded and distributed incrementally, we don't have to repetitively download various versions of the same library from different CDNs for different websites, which will save a huge amount of Web traffic.