ncarlson.dev@gmail.com
546 karma · joined November 14, 2008
ncarlson.dev@gmail.com
I'm curious what you mean by higher level thought (or reasoning). Can you elaborate or provide some references?
That's not my problem. That's your problem.
So, some engineers just stumbled upon LLMs and said, "Holy smokes, we've created something impressive, but we really can't explain how this stuff works!"
We built these things. Piece by piece. If you don't understand the state-of-the-art architectures, I don't blame you. Neither do I. It's exhausting trying to keep up. But these technologies, by and large, are understood by the engineers that created them.
The headphone jack was putting the additional risk on your device to be crushed.
Can you expand on this? I'm assuming the force required to collapse the 3.5mm cavity would be incredibly high. Jacks themselves were good spots to break due to mechanical stress, especially the cheap ones.
The same can be said about the lightning connector. It was literally stopping any innovation. Without the jack, new alternatives will pop up at an incredible pace.
This is forced obsolescence. Suppose the jack remained in iPhone 7. Apple would have a much harder time selling wireless earbuds. Ask HN: When did the terms Front-End, Back-End, and Full-Stack become prevalent?
1 point by ncarlson 2 hours ago | past | web | discuss
Ask HN: How can I self-publish talks like InfoQ? (Software question)
1 point by ncarlson 1531 days ago | past | web
Ask HN: How do I prevent repetitive strain injury (RSI)?
1 point by ncarlson 1832 days ago | past | web
Ask HN: Is it just me, or are HN comments becoming more and more negative?
74 points by ncarlson 2497 days ago | past | web | 157 comments[1] https://stargazerslounge.com/topic/210686-moon-with-de-bayer...
* A monochrome sensor option
* Better sensor documentation. Where are the quantum efficiency graphs?
* Larger sensors.
* Less emphasis on megapixels, more emphasis on efficiency.
* Exposure control in microseconds
* Binning
* C, CS, or F lens mount. Heck, I'd even accept a M12 mount, so long as the lens isn't glued into place.
> JS: { x : 2 + 3, y : 9 }["x"] * (11 + 23)
> Lua: ({ x = 2 + 3, y = 9 })["x"] * (11 + 23)
> Lua: ({ x = 2 + 3, y = 9 }).x * (11 + 23)How?
Is this an honest question, or are you alluding to the idea that someone who doesn't understand PKI should not use distributed source control?
> 1. It's magic box coding (as in I put these simple commands in and the environment just handles it for me and I have little idea how)
Is this not abstraction? I'm not familiar with the internals of the Python interpreter, but I'm able to be productive and creative with it.
> 2. It (by Microsoft's admission) hogs bandwidth. In the desktop world that wasn't a problem but in web applications its a big one.
I'm not convinced that this is a problem outside of edge-case scenarios. However, from my understanding, this limitation is overcome in two ways: 1. Large application are broken up into small modules which can be loaded lazily. 2. Time. The average bandwidth of an internet user increases exponentially over time.
This is the crux of the argument, and no sources are provided. If you're going to write a persuasive argument based on empirical data, you need to cite your sources.
* Nice mechanical pencils
* A Feynman book
Do these comments do anything to further discussion?
My question would be, are individual Dwolla accounts protected on a per depositor basis? Or, is it just Dwolla Corp's own bank account which is protected under FDIC. Their website doesn't make that clear.
It's entirely possible that user funds are stored in a bank account, owned by Dwolla, and that bank account is FDIC insured. If that's the case, then that bank account is only insured up to $250,000 USD.
However, now that Paypal has suspended Mt Gox's account, anyone wanting to work with that exchange now has to jump through additional hoops by opening up a Dwolla or Liberty Reserve account. Personally, I found these sites to be rather shady looking.