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

It is not really just a kettle. Has integrated tea strainer, you can use it as a teapot.

It is missing a proper tea cosy, however.


Major confusion for me, as SPICE is well known circuit simulator: https://en.wikipedia.org/wiki/SPICE

Using it often. Mostly via ngspice nowadays: https://en.wikipedia.org/wiki/Ngspice


I would never call a software project SPICE; I use a fucking search engine when naming things to avoid the cringe of ignorantly landing on a dupe. (And also use SPICE in the LTSpice incarnation; I should give ngspice a spin one of these days.)

Agreed. The SPICE electronics simulator is over fifty years old, and is still very important to people who have to design electronics. It's inside many other electronics design tools. It's standard enough that when a manufacturer comes out with a new analog IC, they often provide a SPICE model for it. Otherwise nobody wants to design it into their circuit. Reusing the name for another program is like calling something new FORTRAN.

(I had nothing to do with SPICE, other than as a user. It's by Laurence Nagel, and I'm John Nagle. Not related.)


We could speedrun this and just call every product "the thing".

That name's already used by an even older technology: https://en.wikipedia.org/wiki/The_Thing_%28listening_device%...

You're absolutely fucking right.

Ngspice is okay but it's a bit clumsy switching between it and xschem.


[flagged]


I know what SPICE is, but for anyone not knowing it, the first SPICE text is also a hyperlink. Clicking it brings the clicker to the homepage instantly.

This is how it should be done: Hyperlinking pages to prevent information duplication and inconsistencies, using libraries to not rewrite every piece of code when it's required.

It passes the sniff test, and a low-color palette of a pony reading a Red Hat checks out pretty nicely.

Maybe we should entertain ourselves sometimes. I don't care about people's choices as long as it's universally unethical or offending or... you get the idea.

Edit: BTW, That pony is the user's general avatar, it seems. Fun.


Seeing a fetish in random cartoon characters ironically tells all of us way more about you than it says about me ;D

This is a poor retort considering how well known and infamous "MLP" and "bronies" are on the internet.

Any you spent more time writing that comment than it would have taken to click the "SPICE" link next to that pony image logo, wait the ~1 second it takes to load, and read the first sentence which would have told you what it is.

Once interviewed for an automotive embedded software position and they asked me if I was familiar with SPICE. Naturally assumed they meant the circuit simulator, answered yes and they did not dig deeper

Only later in the job I realized that they had meant Software Process Improvement and Capability Determination.


It is called ASPICE.

"The abbreviation SPICE stands for Software Process Improvement and Capability Determination. Automotive SPICE (also commonly abbreviated as ASPICE) combines a process reference model and a process assessment model in one standard"

https://en.wikipedia.org/wiki/Automotive_SPICE

In automotive it's known as SPICE, because the automotive is obvious.


dEtermination. Also quite confusing.

They’re only concerned with capability determination, not name determination. Some people just have no SPINE when it comes to naming things.

People who work with virtualization on Linux will (hopefully) all know what SPICE is.

Edit: typo


People who know what both of them are (hello) still won't know which one the headline is talking about.

The circuit one is definitely older, probably has more users, and is just as relevant in this forum.


> with visualization on Linux

You mean ‘virtualization’ here, I guess.


Nope. I work with virtualization on Linux every day, and have done so for many years (and many varieties of virtualization). I didn't recognize it by the name, and I don't remember hearing about it before.

Yes, a circuit simulator.

Indeed, it was what we used in digital circuits lab exercises back in the 90's.

I am happy I am not alone in this

Has been done for decades. Buried capacitance materials like FaradFlex MC12TM exist and are really good, but are not too often used.


Length of this capacitor is close to half-wavelength of 220 GHz (in vacuum).

Using siblings of this broadband capacitor (40 GHz, same package) in some designs. In assembly, those require decent process control. This 0201M package is closer to 01005 passives in pad size. Typically no solder paste is used, just flux. Solder mask alignment has to be very tight (thin web used as a dam only).

Cost per cap is reasonable where it is actually needed, other parts of the system are often orders of magnitude more expensive at those frequencies where performance matters. Where it gets the very high performance, is pillars/channels etched into silicon quite similar to how DRAM capacitors are made, just a “little bit bigger”. This allows for very low inductance and thus very high resonant frequency.


> Typically no solder paste is used, just flux.

Ah, so reflow the solder on the package ends then? And I assume they have a fancy precision process for “tinning” the ends?


The (more common) package has very precise solder bumps. You can have a special order for one with ENIG finish as well, but this only makes sense if you have a really good use case (using Pb solder, wirebonding directly). Not sure what method is used to deposit this solder. Probably just stencil on wafer before slicing.


One scanner has way more than one channel…


0.018 kilotons. Order of magnitude smaller at minimum.


Jobs would have been lost with that move...



Have you tried Affinity Photo?


Affinity is great for editing but doesn't do the library management stuff that Capture One/Lightroom etc do.


I haven't, but based on the history summarized in this post[0] I'm guessing they will soon force everyone into their subscriptions anyways

[0] https://mg0x7be.github.io/affinity-enshittification-how-canv...


2/156 lost for Soyuz in 59 years, 2/135 for Space Shuttle in 30 years. Same rate. People often underestimate how intense STS actually was.


The 2 were early, and fewer lives were lost. The shuttle was unnecessarily risky , and NASA was aware from its inception


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

Search: