HNHacker News
TopNewBestAskShowJobs

qewrffewqwfqew

129 karma · joined August 9, 2014

submissionscomments
qewrffewqwfqew··on Removing support for Emacs unexec from Glibc
First I've heard of unexec() -- while it sounds like a good thing to be rid of, I'd be quite interested to read about its design and perhaps past implementation challenges. Anyone aware of a good tech article on it?
qewrffewqwfqew··on Coroutines and Fibers: Why and When
Under what language / toolkit? Folks are pointing out counterexamples below and I could name a few myself, but I'm curious where you're coming from :-)
qewrffewqwfqew··on Heteroglot: Project Euler problem #16 in Pascal, #17 in Inform 7
Bear in mind that this was written in 1981, at the beginning of a decade that saw enormous progress for Pascal, rendering most of "some guy"'s objections invalid. ANSI C only happened towards the end of that decade.

I think when an essay from 20 (or 35) years ago claiming "X sucks" is referenced, it's kinda foolish not to draw attention to the history that followed.

qewrffewqwfqew··on Windows Remote Desktop Protocol Security Bypass Vulnerability
> The most severe of the vulnerabilities could allow remote code execution if an attacker is able to log on to a target system and run a specially crafted application.

That reads to me like "RCE if you have RCE". Which I guess is a fair description of the DLL vulnerabilities if you ignore the privilege-escalation parts.

The DirectShow and (perhaps) passwordless RDP vulnerabilities seem rather more severe to me.

How is that leader quote appropriate?

qewrffewqwfqew··on ES6 is Over-Engineering JavaScript
> In many ways ES2015 is starting to look alot like other modern programming languages - that's a good thing.

That depends on how you view Javascript.

If you consider it a programming language, the growing-up is a good thing. Making developers more productive and all that jazz. Of course, core WATs in JS are at a deep enough level that they're going nowhere (backward compatibility folks!), and anyone who's not already invested in JS should have the sense to look elsewhere.

If you consider it a runtime for delivering applications to the browser, it's really not so clearly a positive. A more complex language means more lock-in to existing runtimes, more room for bugs, more wasted engineering effort supporting the moving standard, less opportunity for lighter abstractions or more declarative assets amenable to static analysis ...

qewrffewqwfqew··on A rant about application configuration
+1. I knew what I was going to see before I clicked on your image, not because I browse a lot on mobile, but because I use a tiling WM with my browser at ~50% width, or around 900px.

That's enough to get most "responsive" websites showing with no left margin at all, which looks fucking awful. Worse still, half the time I get a hamburger menu and mobile-style navigation!

Apologies for not adding anything to the conversation, I just had to rant about another web anti-pattern :(.

qewrffewqwfqew··on What is a Procedure? [pdf]
> Is there REALLY a difference between a "method," a "procedure," and a "function" proper?

The context you are speaking in entirely determines the answer to this question.

Your context reminds me of "is there REALLY a difference between a 'list', an 'array', a 'tuple' and a 'vector'?", as different languages overload these terms with different (sometimes the same!) properties.

The OP seems to be taking a perspective embedded in operational semantics, where a non-halting, unspecified or incorrect "named callable" should not be properly called a procedure.

Personally, I find both kinds of hair-splitting semantic arguments a waste of time when they're isolated from the underlying question, which should be:

> what sort of conversation do we want to be having about these things? What notation or terminology is going to make that easier?

qewrffewqwfqew··on Little Forms – an open source minimalistic GUI widget library written in plain C
Not sure where you're quoting from, but January 2011 is the oldest entry in the fossil repository:

http://runtimelegend.com/rep/lforms/timeline

qewrffewqwfqew··on Using and abusing Renoise as a demosequencer
It also hijacks what seems to be every other single keystroke. None of F11, ctrl-W, ctrl-L, alt-D, ctrl-plus, ctrl-minus work.

At least on Firefox. Chromium seems to respect the user a little more.

qewrffewqwfqew··on Gmail, We Need to Talk
They killed usenet off good by providing a reasonable interface that encouraged people to link to it .. then destabilising the URLs. I've seen wiki links to google groups that have been changed 3 or 4 times before people simply gave up trying to re-find the original target.

Pisses me off no end.

qewrffewqwfqew··on Long-Term Exposure to Flat Design:How the Trend Slowly Decreases User Efficiency
> for fear of looking bourgeoisie

Nice characterisation, I might re-use that.

Surely somebody has done a study of this effect. In web and software design it's particularly hilarious (in an I-want-to-cry way) since so much good sense has been written (Tufte etc) which is completely discarded by these trends. I expect the same is true in architecture, only I'm less familiar with the literature of that domain.

qewrffewqwfqew··on Gmail, We Need to Talk
I've become convinced that gmail's goal is not to improve email, but to extinguish and replace it. This article talks about one minor aspect of that. In addition:

* breaking established addressing conventions. Gmail (last time I used it) made it difficult to distinguish between To: and Cc:, both in received emails and when sending.

* messed-up quoting, and other broken conventions.

* the one that's been discussed to death here recently: it's on the way to impossible to send email and expect it not to be silently dropped if you're not on gmail.

* the email authenticity measures linked to the last point also screw up mailing lists and forwards. Most of the DMARC notifications I get from gmail now include a bunch of FAILs for people that forward from another domain to gmail. Soon, they'll simply stop receiving most mail.

Email is walking dead, and gmail is largely to blame.

qewrffewqwfqew··on Long-Term Exposure to Flat Design:How the Trend Slowly Decreases User Efficiency
Love it. Well said.

This trend of design fashions negatively impacting usability has become so blatantly visible across the web (and apps, and desktop interfaces) during this century that I've become quite curious what psychological/organisational effects are at force.

Are there historical examples of the same tendency that can be examined? Tools, signage, forms or public spaces becoming a progressively more difficult and less usable mess under the aegis of "making things easier for users"?

qewrffewqwfqew··on Counting Things in Python: A History
> Per the Zen of Python, “there should be one– and preferably only one– obvious way to do it”. This is an aspirational message.

"aspirational" is an optimistic way to describe it. As the article illustrates, every ~2 years the "pythonic" approach is different. Innovation is good, but it hurts re-use of code and of skills.

qewrffewqwfqew··on Tell HN: Some .tk domains have been hijacked
In clickable form:

http://wiki.tcl-lang.org/ (also https://tcl.wiki/ )

https://tcl-lang.org/

http://core.tcl-lang.org/

qewrffewqwfqew··on Seizures from Solving Sudoku Puzzles
Plenty. I'd hazard that's how most medical science has come to be.

If you're on this site and haven't already been strongly reccommended to read Oliver Sacks, do so. Broader than neuroscience, look for memoirs of British surgeons during WWII.

qewrffewqwfqew··on The Dynamic Def – abusing Ruby's def statement
For a much deeper exploration of this kind of dynamic object behaviour in Tcl, Sean Woods' "Lifecycle Object Generators" is a fun read:

http://www.tclcommunityassociation.org/wub/proceedings/Proce...

qewrffewqwfqew··on Designing Command-Line Experiences
Tenants are not tenets.
qewrffewqwfqew··on Economics Has a Math Problem
Doesn't (over-applied) machine learning just lead towards a variation of exactly the same problem?

Instead of "this model fits the curve and sounds attractive and sciencey" it becomes "this model fits the curve and was done by computer!"

Not really the "empiricism coming to economics" that the author claims, but I guess it could support better outcomes. For a while.

qewrffewqwfqew··on Pro-security? Stay away from these hosters
A version that has been end-of-lifed and is superseded by three minor releases is a pretty strong indication. The amount of work involved in backporting patches is likely to be significantly more than migrating to a supported version which receives timely patches.
qewrffewqwfqew··on The curious case of disappearing Polish S
One might have thought the OP highlighted the inherent problems in making assumptions about the meaning of meta-keys for all of your users, all around the world.

But of course the OP continued to make the same mistake, which I pointed out way up at the beginning of this branch.

qewrffewqwfqew··on The curious case of disappearing Polish S
The problem is that the decision is left up to the website.

But I see I'm in the minority here, thinking software should be predictable and leave the user a sense of control, so feel free to disregard my opinion.

qewrffewqwfqew··on The curious case of disappearing Polish S
Would you be so dismissive if the overridden key were Ctrl-W?
qewrffewqwfqew··on The curious case of disappearing Polish S
> It should be mostly transparent to the user that they are in a browser.

Even if the browser is providing your entire desktop experience, you should be able to switch applications or close them in a predictable way.

qewrffewqwfqew··on The curious case of disappearing Polish S
So make it opt-in, and highly visible to the user when it happens.

I get a nag screen when videos in the browser go full screen, telling me loud and clear that expected behaviour is changing and telling me how to get control back. When a website overrides keyboard controls, the first I know about it is when I can't scroll properly, or switch to another tab, or go back, or close the window that's yelling at me and making my machine thrash ...

Disruptively changing modes without notification violates fundamental rules of interaction design, affordances and basic security. How is that okay?

qewrffewqwfqew··on The curious case of disappearing Polish S
.. another relevant xkcd: https://xkcd.com/1479/
qewrffewqwfqew··on The curious case of disappearing Polish S
Yet another example of why websites shouldn't be able to hijack keys that have meaning outside them (in the browser itself, or in the desktop environment). It still blows my mind that browsers permit this and don't provide an easy option to stop such abusive (and dangerous!) behaviour.

The workaround is typical of web stuff as well: deal with the symptoms one by one while leaving the underlying problem unquestioned.

qewrffewqwfqew··on EFF’s Game Plan for Ending Global Mass Surveillance
In principle, the NSA is bound by US law. The problem is that US law is broken.
qewrffewqwfqew··on Show HN: Notepad5, a distraction free writing webapp
of all the software that can benefit from being on the web, this has to take the cake.
qewrffewqwfqew··on A Web Developer's Guide to Communication Protocols (SPI, I2C, UART, GPIO)
Twenty years ago you could have said the same of C. I guess that's progress!
← PreviousPage 2 of 3Next →