HN user
The primary goal of this is support for old/obscure hardware with no LLVM/GCC support. There are still some systems out there that don't support Rust but support C.
The landing page mentions Plan 9 as one of the systems.
There goes my coding assistant (removed by US gov't). It was useful while it lasted. (eye-roll)
My personal experience of Fable 5 doing its own thing has been very positive.
I was trying to find the root cause of a crash in a Python module which left no errors in the log or console. Fable wrote a test harness that simulated clicks in the UI, then bisected my code until it found the point where it started crashing. It exaggerated the cause of the crash, then ran a series of bash one-liners to make Python virtual environments under `/tmp` for each version of that Python module until it found one that did not crash.
It went way deeper to root cause discovery (a regression in the module causing a heap allocation overflow) than I could have done myself, provided enough info and a simplified example to raise a bug report and then wrote a work-around to prevent that from happening in my application.
I don't let it run completely loose; I review each CLI command it wants to run and I append answers to the "yes" continue action (if I have them) to prevent excessive token use.
Install Windows 11 ARM under the macOS "UTM" App. This lets you run x86 Windows programs on Apple silicon.
If you want to experiment with KANs yourself in a non-FPGA environment, there's a GitHub repo here: https://github.com/KindXiaoming/pykan
HN comments page on that is here: https://news.ycombinator.com/item?id=40219205
Greg Egan writes novels with plots that revolve around high-end science, physics and mathematics with some very wild concepts and conclusions. Even better, he has animations and illustrations of some of his books' concepts on his website for those that want to go deeper.
I hadn't noticed his Miscellaneous Fiction section, so this is a nice rabbit hole to find.
“Sent from my iPhone” is a default signature, but you can change the message under Settings -> Apps -> Mail -> Signature (at the bottom of the options page)
My /usr/bin/ folder wants to know which bit gets italicised :)
Very impressive that I can sketch a character in the top-left and get a close match. That's a real highlight showing that there's more going on under the hood than a big look-up table.
I love the photo of the probe, and I bet it's very expensive. I wonder if the "A071626" sticker changes the impedance of the traces enough for you to notice :)
https://www.mattkeeter.com/blog/2022-08-11-udp/probes_full.j...
Thanks, I get it now.
I took a look at the https://tvnfo.com/ site and I have no idea what's behind the donation wall. Can I suggest you have a single page which explains or demonstrates the content, or there's no reason for "new" people to want to donate to get access.
I had to replay that to appreciate how the transitions from night to day were done so very, very well. The dynamic range of the shots always seemed spot on.
That isn't easy to get right.
Yes, IP usage is awkward and tricky. You can use the GUI to make the initial .xci file or .tcl file, but when you build a project, you need to use the same version of Vivado that the IP core was originally created in. Xilinx have improved that a little with 'write_ip_tcl' and 'write_bd_tcl' now having flags that let you ignore the version (or minor version). I've not had time to try those yet.
I've managed to make nice 'make' flows for Vivado, ISE, Quartus and DC. Libero took a bit more poking, but it's also possible.
The GUI interfaces are what newcomers tend to aim for straight away, but they're not good for any long-term "repeatable" build flows and they're no use for CI. I think this is where a lot of the frustration comes from.
# Here's the general flow for Vivado TCL projects that takes you from source code to a bit-file with no interaction. Read UG835 for details.
create_project -in_memory -part ${PART}
set_property target_language VHDL [ current_project ]
read_vhdl "my_hdl_file.vhd"
synth_design -top my_hdl_top_module_name -part ${PART}
opt_design
place_design
route_design
check_timing -file my_timing.txt
report_utilization -file my_util.txt
write_checkpoint my_routed_design.dcp
write_bitstream my_bitfile.bit
This article is a rant about how bad tools are without going into specifics. "VHDL and Verilog are relics", well so is "C" but they all get the job done if you've been shown how to use them properly.
"engineers are stuck using outdated languages inside proprietary IDEs that feel like time capsules from another century.". The article misses that Vivado was developed in the 2010's and released around 2013. It's a huge step-up from ISE if you know how to drive it properly and THIS is the main point that the original author misses. You need to have a different mindset when writing hardware and it's not easy to find training that shows how to do it right.
If you venture into the world of digital logic design without a guide or mentor, then you're going to encounter all the pitfalls and get frustrated.
My daily Vivado experience involves typing "make", then waiting for the result and analysing from there (if necessary). It takes experience to set up a hardware project like this, but once you get there it's compatible with standard version control, CI tools, regression tests and the other nice things you expect form a modern development environment.
LMStudio? No, it's the easiest way to run am LLM locally that I've seen to the point where I've stopped looking at other alternatives.
It's cross-platform (Win/Mac/Linux), detects the most appropriate GPU in your system and tells you whether the model you want to download will run within it's RAM footprint.
It lets you set up a local server that you can access through API calls as if you were remotely connected to an online service.
OK, I take it back now that the HN hug has died off a bit. Bruno's site is a ridiculously neat thing to see in a web browser.
I can't see Bruno's site and I assume it's because of the HN hug of death, but an impressive 3D website that always comes to mind is acko.net, with its 3D rendered tubular logo. He even describes how it was done in a blog post.
In the past, I'd find one wrong answer and I could easily spot the copies. Now there's a dozen different sites with the same wrong answer, just with better formatting and nicer text.
I have to do tech support for grandma. Every few years, her Windows laptop gets so slow that we get her a new one. This time I will test out a switch to Linux instead of buying a new computer. Zorin is the most attractive option because it's the least strange.
Just a warning that the video ends with a loud, high pitched tone that will make you want to rip your headphones off.
Ironic for a video about hearing.
Helping me get up to speed with an unfamiliar API much, much faster than any online searching.
I can describe an example application and see which API is chosen, along with which functions/methods are called and in what order and with what data structures.
I take it from there and build on that by hand. Take Python UI development, for example. I can ask for a window with a zoomable bitmap image with scrollbars. I get an answer I can refer to in seconds. If I know that I want PySide6 or PyQt6, I can specify that, or I can ask for a list of Python UI APIs and their strengths/weaknesses.
I'd switch to semicolons, but I need to re-read this book to be sure I'm using them correctly:
Switching the font on apple.com to Comic Sans is a nice touch.
https://www.fuckupmysite.com/?url=https%3A%2F%2Fapple.com&to...
That fine needs an extra zero on the end. They'll shrug it off as the cost of doing business.
I got the Australian one by replacing `cn` with `au` in the link.
https://apps.apple.com/au/app/ublock-origin-lite/id674534269...
This CODEC uses the same base algorithm as HTJ2K (High-Throughput JPEG 2000).
If the author is reading this, it would be very interesting to read about the differences between this method and HTJ2K.
For reference, here is the MSIX Toolset code repository: