grawp
grawp on Hacker News
It's not 'supposedly'. It's a feature they officially gained just a few crewed flights back. It's a mean of last resort and has to be manually committed to during descend. I assume it may have to cut any remaining or semideployed parachutes.
I've been using Helix for some months now but haven't touched Rust. For that I plan to go temporarily back to vscodium + rust-analyzer + probe-rs which I know is a crazy good combination (no stinky openocd configurations, no gdb and connecting it to one of gazillion debug plugins - probe-rs has its own DAP thingy).
In meanwhile I'll look into neovim and making its selection model more like in Helix. For me it's not about motion before verb... I can use visual mode etc.. but about having consistent advanced commands for refining multicursor selections like selecting in selection, searching in selection, spliting selection to even more cursors or collapsing touching selections into one etc.
I want to like Helix. Its sane defaults are good. Selection model is even better and superior to everything else.
But its lack of proper API and total lack of server-client model makes it just completely unusable.
I've seen people trying to integrate it with their file browsers, file trees, terminal multiplexers or window managers but there is just no normal way to get data into a running Helix instance other than sending keypresses and absolutely no way to get data out of it except of reading its screen. Its basic premise is just absolutely horrible which is of course completely subjective.
Another dealbreakers for me are absence of a proper debug support, code outlines, memory views, variable watchers, registers views etc. for working with embedded (as in running on microcontrollers) Rust.
https://www.rust-lang.org/learn
and there is a
whole official book with detail explanation and first principles about what you ask.
Learn to use obvious "entrypoints" first which are cmdline help, manpages, and official web documentation instead of searching the web first. Those TONS of tutorials about embedded rust are uninformative at best and actively harmful at worst.
If you plan to use Cortex M based microcontrollers then there is rtic.rs async framework / RTOS. It could teach even 95% C programmers how hopelessly underused/misused NVIC in those core usually are.
Then if you need drivers with bells and whistles there is another async framework / RTOS called embassy-rs but you can combine those drivers and subsystems with rtic.rs async engine.
EDIT: Don't imagine async engine on MCU as some costly abstraction. It's zero cost abstraction for embassy-rs when compared to traditional RTOSes and negative cost for rtic.rs since traditional RTOSes does not use dedicated hardware machinery for scheduling which is present in Cortex M cores.
It is not so strange. Game journalism is mostly completely out of touch with majority of gamers and often part of 'woke' echo chambers with their fallback usually being blaming things on review bombing and other problems.
Fortunatelly we have free market.
Yes it is and it is not the first time having such contigency plan.
Quite recently there was a Soyuz with crippled cooling and the contingency plan for the American astronaut that came with it was to evacuate via Dragon if there was an emergency before new Soyuz arrived.
Do you realize that 10 F9 flights means 10 new second stages and on those second stage someting has to sit and that something whatever that is - is completely dwarfed by ISS and it would have to be a new dedicated vehicle consiting of mostly fuel just to deorbit the sucker in one go.
Original plain AFAIR was to use several Progress vehicles.
And going to graveyard orbit with something like ISS is not just a few whole times more difficult but at least an order of magnitude more.
I use window manager for tabs as it should be. No need for some stinky multiplexer.
There does not seem to be any release tag or branch nor production gerber files.
I was hoping to get my hands on some functional DVI/HDMI controller. Well never mind, I'll wait.
Wake me up when it can do precise 400led 2D mapping under 10seconds and even not be picky about ambient lighting conditions at all like Twinky.
Cyclist in Czech and Slovak republic are much more often assholes than the drivers. There is a very large group thought not a majority of cyclist who blatantly disobey traffic laws and are completely arogant (they are saving the planet of course! they don't have time to even slow down before pedestrain crossings, use sidewalks when they feel like even thought is strictly forbidden and never ever use bike lines even in situations where law absolutely requires them to and even when it is wide and of a same quality as a road nearby, often use pedestraian crossing themselfs even thought it is strictly forbidden for a mounted/riding cyclist just to kinda have a right of way when they would otherwise have to yield on normal road before turning (pedestrains DO have a right of way before cars on zebra crossings without lights)) and some of them out outright agressive and physically dangerous (maybe because they are pumped with hormones and adrenaline?). There was a quite recent case where a male cyclist (before his own kids and wife!) brutally broke a pedestrian's jaw because the pedestrain notified him that they are illegaly cycling on a sidewalk and they the cycling family disappeared. Police's detective work lead to his apprehension months later.
Also absolutely wonderful documentation directly from Nordic Semi (for the peripheries) and from ARM (for the basic core).
Non-obscure architecture, one of the most used Core in the world (Cortex M4), true Floating point coprocessor, non-chinese firmware for BLE, if are not afraid of doing full certification it can also be non-proprietary Wonderfull documentation. Ready made modules can be obtained at the same price as ESP32. You support EU chipmaker.
LEO is not accessible by space elevator at all. If you got off at ISS height you would just fall down.
Good for basejumping though. And no you wouldn't even need heatshield, just rugged EVA suite.
I have the exactly opposite experience. Rust move semantics, borrowing, Send&Sync types and checks and type based compile time state-machines is exactly what I was missing
specifically on embedded systems in C/C++ and what I'm sorely missing in Zig.
In Rust you start by splitting peripheries to blocks, then to registers, then to register parts and distributes these (these are zero cost operations!) into irq handlers and tasks and the type systems will check that everything that need exclusive access has it .. that you do not use read-modify-write operation on a same register from two interrupts where one can preempt the other without using some guard as mutex.. while it perfectly allow you to do this with write-only registers without guard etc... it is just so nice to work with.
People who find it complicated and/or not worth it are usually doing either some rudimentary super duper easy stuff on architectures or OSes which does not have or utilize nested interrupts or they do it on some IOT like noncritical stuff where they don't give a s** (vs industrial machinery, drones, other vehicles..).
I'm still waiting for the AP mode :(
NO. He asked about Nix NOT NixOS... do not conflate them together. Nix an extremely generic tool for much much much more than what you have said.
- Nix is a purely functional language with lazy evaluation.
- One of its types is a derivation which is basically an immutable result of some script / application / other build system ran in sandbox with exactly specified environment.
- Calling derive with same inputs generates same derivation.
- It's lazy... only when something tries to access derivation's files or other properties its build script is run.
You can use derivations as (/ to represent)
- packages
- generated configuration files / settings
- containers
- whole OS images ... e.g. I'm building raspi SD card images using Nix.
Sry but that is just some completely optional 3rd party library.
Zig has been compiling to AVR targets sucessfully for a very long time.
Zig doesn't support AVR? It's news to me since I was using Zig on Atemega328p a whole year ago and even with true debugging via debugwire in VSCode.
Rust is definitely NOT a higher language than C and there are dozens of OSs like TockOS, R3 and OS-like frameworks (like embassy-rs and RTEMS-inspired RTIC) written in it in the embedded world and quite a few in nonembedded world (i.e. world where you have MMU not just MPU or less).
Spirit and Opportunity were rovers and constantly changing place and position.
Insight is NOT a rover. It is an unmovable lander.
Insight is NOT a rover. It's unmovable lander. There's so much less to gain post primary mission. And last two rovers outgrown solar panels anyway and are powered by thermoelectric generators powered by radioactive decay.
Insight is NOT a rover. It's stationary unmovable lander.
You should NOT use writable FS (except for a specialized one on a separate partition/device for user settigs) even with EMMC! And then you don't need battery backup.
Using writable rootfs goes against industry practices and is a disaster waiting to happen... like the one with emmc in Tesla's central panels.
Because there are not thousands of existing routers supporting openwrt.
OpenWRT needs at least 64MB RAM now and most consumer oriented crap which has that amount of RAM is expensive and under same model number you always have revisions galore most of them unsupported and some even of completely different architecture than other revisions.
Many times there is less than 50% chance that you buy a supported revision unless you go with things like Turris Omnia or Raspberry Pi..
Same mechanism why you get more sick in the winter. Periodic thermal shocks and therefore periodic capillaries expansions and retractions in you airways, sinuses.
People are quite susceptible to it here in central EU, me included. US people seem to be kinda conditioned to the constant thermal shocks.
Here many only have and use AC in their cars and only in peak summer and I remember there used to be warnings in TV news that you should turn off or start gradually decreasing AC intensity before arriving to your destination a getting of your car. (It was usually as a part of some interview with some GPs, discussing why are people getting more sick in peak summer.)
My reaction was only meant as a response to @Sanzig calling PIOs innovative.
The logic analyzer itself, even the usage of cheap Pico in it is very cool.