I’ve had cases where the live coding session is collaborative and easy going. And cases where the interviewer scowls, chews on their fingers, or constantly scratches themselves.
After one particularly distracting interview, I explained to my partner that a live coding interview is like filming a porno to prove you’re good husband material.
Ive been collecting Model M and Model F keyboards from IBM off from Ebay over the last few years. I've got quite a collection now. Only the IBM manufactured keyboards, no Lexmark or third-party.
I remember typing on a Model M as a kid. My fingers pushing the empty spaces between CTRL and ALT, where on newer keyboards, an OS meta now lives.
I remember writing Basic. Then Turbo Pascal. Full of curiosity and wonder.
The IBM authentic keyboards have a badge on the back with the year and month of manufacture. Most of these keyboards are older than my co-workers. Many still function correctly.
I'm guessing you're talking about Julian. What's interesting in this case, is that Julian refused to let himself get arrested which would have brought him to court and due process.
But that's not what happened in Canada. With no due process non-violent people were unbanked, simply for protesting against the government.
Simply speaking, Visa and Mastercard debanked Wikipedia because of their journalistic activities, simply because the US government did not like them, before there was any judicial process whatsoever.
I'm specifically thinking about political protestors. Such as BLM. Or No Kings.
Their right to political protest is protected and VC/MC isn't going to un-bank them without a court order. And since their right to protest is protected, that's unlikely to happen. Unlike Canada.
The Government was unhappy with them because they were occupying the capital, blocking border crossings, and their MOU demanded that Parliament be dissolved, and that Senators and Bureaucrats who disagreed with the MOU resign; under the threat of the Governor General not allowing Parliament to sit again.
It was entirely warranted to freeze their accounts and make arrests.
And when other protests like BLM caused huge public disruption during a pandemic the government did nothing. It was entirely a political response.
In a free society people should be able to protest whatever in public without getting arrested and debanked. Otherwise you might as well be one of those authoritarian countries where protesting requires a permit.
Different country, different Government, different protests.
BLM was a nothingburger in Canada. The most similar protests to that would have been the Wet'suwet'en solidarity protests. Those lasted a few weeks and were ultimately resolved peacefully, for the most part. An important thing to consider is that the protestors weren't interested in toppling the Government; they simply wanted the Government to hear them.
Not the original poster, and I don't have very high hopes that these will be revisited, but some things I would like to see revisited are:
- ability to define anonymous functions without having to put it inside an anonymous struct. I get the argument against closures (even if I don't fully agree with it), but not having first class support for anonymous functions feels pretty regressive for a modern language
- have a way to include payload data with errors. Or at the very least, define an idiomatic pattern for handling cases where you have additional data for an error
- allow struct fields to be private
- bring back async support in some form (this one I do have some hope for)
I would like to have some kind of interfaces instead of having to always use anytype, so compiler errors will appear in the call site instead of the called function body
(That link seems to show the "unused local variable" error line twice for me; that's some kind of bug with this zigbin service and does not reproduce when running the Zig compiler normally.)
I think this should be a warning on debug builds and an error on release builds, but it's a relatively minor thing and not a deal breaker by any means.
If this is the worst thing that people would like to see revisited, Zig must be doing amazingly well.
> but it's a relatively minor thing and not a deal breaker by any means.
It totally breaks my normal workflow. I don’t use zig at all because of this misfeature. Warn in debug and error on release builds would be strange but fine.
reply