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

Relevant xkcd: https://xkcd.com/1545/ (sorry) ;)


As an Australian, it also baffles me. We withdrew 1 and 2 cent coins from circulation in 1992, and prices are simply rounded to the nearest 5c when paying with cash. Maximum 3c difference per transaction, which averages out in the long run.


Yeah, NZ phased ours out late 80s/1990. 2004 we phased out the 5c piece as well.

Anecdotally (as in I might be wrong :) I remember hearing at the time the 5c piece was phased out it was worth less than when the 1/2c pieces were originally released. NB I have put zero effort into thinking if that makes sense or is true. (edit - confirmed)

[ Edit ] - We also made every other coin smaller. It's always startling to get an Australian 50c coin - even though it's the same size as ours used to be. Our's is now smaller than the AU 20c.

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


I'd say 99% of my transactions are apple pay now, with 1% being rare place that doesn't take paywave. I still have couple buck of cash for those super rare cash purchases on side of the road (damn they need alipay or something like that - NZ is kinda stuck with 'good enough' banking and failing to see innovation from Revolut and the like in Europe - that said surprised how much cash still used in Europe).


>and prices are simply rounded to the nearest 5c when paying with cash

In Canada as mentioned already in the comments we phased out the penny no more made after February 4, 2013.

But many business still today (Oct 2020) have items with prices ending in penny amounts. If you pay with cash it's rounded up or down but if you pay with debit, credit, or cheque the penny amount is used. Stupid because there's no incentive (ha pun!) for businesses to change (double pun!).


"Evil Mode: Or, How I Learned to Stop Worrying and Love Emacs" by Aaron Bieber is an interesting talk on switching from vim to emacs + org-mode.

https://www.youtube.com/watch?v=JWD1Fpdd4Pc


Thanks, I just watched the video, and it did intrigue me enough to install spacemacs to start playing around with it.

Having "real" spreadsheet like tables within my wiki does look appealing. I do in fact already have a bunch of small spreadsheets doing some very basic stuff, and it does make more sense for them to be within the wiki itself.


> What this author has settled on looks very similar to commonly used tiling window manager shortcuts

This is what really intrigued me about the article. Most are about remapping the prefix to something easier to type, or using more intuitive mappings, but removing the prefix altogether is different.

I think I might try it for a while. I'm kind of in two minds - on one hand it shortens common actions from a chorded prefix + a chord to a single chord. On the other hand, it makes it easier to clash with existing keybindings and modifiers (readline default bindings use alt/meta and ctrl, my i3 config uses super, other cli apps use ctrl...). It also means I need 2 sets of muscle memory, because I use tmux in many servers and such where I don't have the opportunity to add custom config.

> I guess the funny thing is, this gives a nice bunch of Tmux shortcuts, unless you're using a tiling WM for your system , in which case this is hopeless

Unless you use a different modifier for the tiling wm actions - eg. I use super + <keys> to namespace i3 bindings, which leaves alt/meta free for readline and others.


> If something I need is added to Rust 2018 or a later edition, I'll be forced to update or backport.

Should add that new editions with breaking changes are only expected to happen rarely (iirc every 3 years), a large difference to 6 weeks.


> Wouldn't everyone be better off if that language was Rust itself, and people who don't want to write that "modern code" ... don't?

Agreed. The author's whole argument of not wanting "having to make these superficial changes again and again" doesn't make sense. There isn't any requirement for all code to follow the latest and greatest idioms. Rust guarantees backwards compatibility, and the author even acknowledges that in the article.

It would be pretty sad if the reason for no new features or syntax in Rust was due to programmers not wanting to feel like their code was no longer idiomatic.


I think it depends on whether you are working full time in Rust or as a hobbyist trying to break in.

I gave up on EmberJS around the same time because I only got a five hour chunk of time every couple of weeks and they were making semantic changes so frequently then that it felt like I spent half of my time upgrading my code to work with the changes. It ended up being a major factor in killing that project for me and I’m just now getting back to it.


Low-investment hobbyist Rust projects don't need to be idiomatic. Rust hasn't broken backwards compatibility except for a few soundness fixes that broke hardly anyone. It sounds like your EmberJS experience was pretty different.


Wow, he said he got stuck with Rust 2015 and I thought Rust wasn’t keeping backwards compatibility, like earlier Swift. Not cool.


I've been using Rust since 2015 and never had to update anything.

The Rust "language version" is a per translation unit setting, and Rust supports having multiple library versions in a binary.

So when I want to use a new language feature, or want to use a new library or library updated to use a new language feature, I just do so in the next translation unit I create. Creating a new translation unit always defaults it to the latest language version (unless you specify otherwise), so this is a quite laidback low-friction approach. I tend to create at least one translation unit per month.

If I had to update all my code to use the latest language features I wouldn't be doing anything else full time. This has nothing to do with Rust. I also use C++, Javascript, ... I don't think I would manage.


> I don't know what it's like on the AMD or Intel side

I recently switched to AMD - that, with a compositor (compton/picom), resulted in a super smooth tear-free experience in X for me.

My experiences with Intel integrated graphics has always poor performance, and bad screen tearing, sometimes screentearing even with compton running.


Agreed. The extra security given by the latter is a huge win for Wayland, but it needs to be possible to give access when required.


s/latter/former


Thanks for these comments!

I definitely need to migrate away from NetworkManager; I think you just gave me the motivation to do so. :)


You might find 'nmtui' (Network Manager Text User Interface) more helpful if you prefer an ncurses based interface similar to the GUI nm-applet (but it doesn't work for GUI-only configuration extensions for some VPNs, etc.)

'nmcli' is good for basics, eg:

nmcli == connection summary inc. addresses, routes, DNS

nmcli dev wifi == wifi networks found (inc. specs)

nmcli dev wifi rescan

nmcli con == list configured connections

nmcli con up Connection-Name

nmcli con down Connection-Name

most of the above support intelligent tab-completion including of (space containing) connection names.


FWIW I am using nmcli and it work good enough for me.


Iwd is much better for WiFi.


To clarify, it does support nvidia through the open source nouveau drivers. It's only the proprietary drivers that aren't supported.


You mean it does not support the drivers that actually work?


It depends what you call working. Nvidia proprietary driver has a broken wayland implementation (a choice that nvidia made), whereas nouveau has a working one. Better pick AMD or even Intel GPUs on Linux as drivers are much better.


Yes exactly. I don't recommend nvidia.


This is a good reason to select different new hardware but insufficient to get rid of existing hardware.

If most people agree we can worry less in 5-10 years. Unless people work around it during this time frame in which case people can continue not caring.


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

Search: