Hacker Newsnew | past | comments | ask | show | jobs | submit | kevlened's commentslogin

He's changed wild-type planarians to grow the heads of other species. It reverts after a few weeks, because the system has error-correcting mechanisms, but the DNA of these worms is unchanged.

He once compared tinkering with DNA as pulling out a soldering iron to fix a software bug.

In the case of morphology, DNA may not be the best level of abstraction. It's certainly possible, just as one can use chemistry for social problems, but for some problems, affecting cell-to-cell communication may be a more direct path.



> The only thing I see in the QC space, are QC stocks and funding paying for the employment of scientific experimentation

Then invest accordingly, and later reinvest your winnings in a different direction.


I've had to switch from SSE to WebSockets to navigate a corporate network (the entire SSE would have to close before the user received any of the response).

Then we ran into a network where WebSockets were blocked, so we switched to streaming http.

No trouble with streaming http using a standard content-type yet.


> Find me a “lights out” factory. They don’t exist.

"Inside China's 'dark factories' where robots run the production lines" https://www.youtube.com/watch?v=ftY-MH5mdbw

"China’s Dark Factories: So Automated, They Don't Need Lights" https://www.youtube.com/watch?v=MCBdcNA_FsI


Seriously? They show people on the floor within the first 30 seconds of the video. I guess it’s technically “lights out” if you make people work in the dark, but I meant, and the article implied, production without jobs.


Standard .env is unencrypted, while a dotenvx .env file has plaintext keys and encrypted values. Anyone with access to the repo would also need the DOTENVX_PRIVATE_KEY variable to decrypt the env file.

One key deployed to your hosts means adding new secrets doesn't take operations effort. Also, the process uses a public/private key pair, so adding a new variable doesn't expose existing variables.


I agree. From where I'm sitting, Seedream just bent the neck while Nano Banana Pro actually shortened the neck.


Your example template and the others here are almost jsx after it's compiled (handwritten below). This jsx discussion seems more about removing the compile step, which you can do with https://github.com/developit/htm

    import { createElement as m } from "your-jsx-compatible-library";
    
    var ListComponent = () => {
      let count = 0, selected = null;
      return {
        view: ({ attrs: { items }}) =>
          m("div", null,
            m("p", null, "Clicked: " + count + " times"),
            m("ul", null, items.map((item) =>
              m("li", {
                onclick: () => { count++; selected = item; },
                style: { cursor: "pointer", color: item === selected ? "blue" : "black" },
              }, item)
            )),
            selected && m("p", null, "Selected: " + selected)
          )
      };
    };


> to get sales the company ended up moving everything into AWS because customers did not trust anything else

This is a hidden cost of self-hosting for many in b2b. It's not just convincing management, it's convincing your clients.


That's interesting. Except for $GIGANTIC_CO (like, BofA, or the government), i'd expect a SLA that describes service resiliency and not "well, our service will be up because we're on AWS".

Why would you need to disclose your hosting provider? is that really a concern for hosted services (and if it is, why isn't the customer hosting it in their cloud?)


Most customers do not want to host anything if they can prevent it. My employer was selling the servers that host the entire shebang, and most did not want to host them. We'd explain they'd save a lot by hosting and viewing/streaming everything locally, but their IT people were not comfortable, and their execs wanted to see everything on their phones when not at work. We made it all plug and play, and still they wanted to pay 10-20X more for a web service.


It also increases the cost of martyrdom.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: