61–70 of 177 posts
There are a lot of wireless communication improvements related to WiFi and 5G. I think this opens a lot of doors, especially around low power apps. Also, somewhat related: secure anonymous data exchange has a lot of cool possible applications beyond health exposure tracking.
Earlier quoted context omitted.
Are WebGPU "libraries" at a point where instead of being recommended Python + PyTorch for neural network training (then exporting the model to ONNX and turning around and loading it and using it)? If not, how far? I've had trouble understanding why the PyTorch "GPU" (CUDA, MPS, etc.) code can't convert to WASM + WebGPU. Something has to be missing/it has to be a huge effort, but in theory you're supposed to be able t…
It can be converted, and can be fairly fast, see Tensorflow.js or https://jott.live/markdown/m1_webgpu_perf . However the any “web” standard will always be a subset of what the hardware can truly provide because it has to support ALL GPU vendors. For example leveraging Nvidia Tensor Cores or Apple’s neural accelerator is not possible. For ML training and inference this means that any webGPU implementation is at least…
The WSL in the article was throwing me off.
WebGPU. It’ll be live in Chromium stable this Thursday and will be the biggest step change for browser-based GPU since the original WebGL.
One of the questions I've been asking is we've basically had physical servers -> VM -> cloud -> container orchestration on about a decade long cadence. So what's next--especially considering you can argue a lot of the low-level architectural things haven't really changed during that period. But, then, perhaps architectural details don't matter a lot at this point relative to things like AI/ML. Even WASM is mostly in…
Physical servers (or devices) are next, obviously! IT is cyclical.
Instead of renting a VM or running docker containers you rent a small physical server for each service.
Earlier quoted context omitted.
Physical servers (or devices) are next, obviously! IT is cyclical.
Speaking of cyclical IT, my estimate is going “forward” to the terminal/mainframe-esque concept of simple and cheap “terminals” aka laptops that you use to log into a much beefier “mainframe” aka cloud workstation. I’m at a FAANGMULA and I’ve been using a cloud workstation from my cheap laptop as my daily driver for months now. The VM is so much higher-spec’d than what they would have bought me for a desktop. Just do…
One of the questions I've been asking is we've basically had physical servers -> VM -> cloud -> container orchestration on about a decade long cadence. So what's next--especially considering you can argue a lot of the low-level architectural things haven't really changed during that period. But, then, perhaps architectural details don't matter a lot at this point relative to things like AI/ML. Even WASM is mostly in…
What about 'AI Tendrils' --
I thought this output from GPT was interesting for thinking of the above:
https://i.imgur.com/WsxwuJh.png
and a BOM
https://i.imgur.com/5g1mXfp.png
https://i.imgur.com/MdbQKx1.png
https://i.imgur.com/Bi0PRTQ.png
--
Actually, I asked gpt to recommend additional columns, here is the result
User what columns would you suggest to add ChatGPT
Here are some additional columns that you may consider adding to the HN table:
* Display type: OLED, LCD, AMOLED, etc.
* Display resolution: the number of pixels on the screen.
* Water resistance: the level of protection against water damage.
* Heart rate monitor: whether the wearable device has a built-in heart rate monitor.
* Sleep tracking: whether the wearable device can track your sleep patterns.
* Music playback: whether the wearable device can play music and if it has built-in storage.
* NFC: whether the wearable device supports near-field communication for contactless payments.
* Voice assistant: whether the wearable device has a built-in voice assistant like Siri, Google Assistant, or Alexa.
* Other sensors: such as an accelerometer, gyroscope, barometer, altimeter, or compass.
Keep in mind that the more columns you add, the wider the table becomes, which may make it more difficult to view or analyze. So, you may want to choose the most important columns for your specific use case and audience.
Earlier quoted context omitted.
Physical servers (or devices) are next, obviously! IT is cyclical.
Speaking of cyclical IT, my estimate is going “forward” to the terminal/mainframe-esque concept of simple and cheap “terminals” aka laptops that you use to log into a much beefier “mainframe” aka cloud workstation. I’m at a FAANGMULA and I’ve been using a cloud workstation from my cheap laptop as my daily driver for months now. The VM is so much higher-spec’d than what they would have bought me for a desktop. Just do…
One of the questions I've been asking is we've basically had physical servers -> VM -> cloud -> container orchestration on about a decade long cadence. So what's next--especially considering you can argue a lot of the low-level architectural things haven't really changed during that period. But, then, perhaps architectural details don't matter a lot at this point relative to things like AI/ML. Even WASM is mostly in…
I'm excited by the idea of WASM being 'the thing' because it basically boils down to passing raw executables around, and running them in trusted contexts. It's the ultimate end to the cycle of removing all operating systems.
