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

For most people, the critique of Japan is because their own countries used to operate jails in this way.

So rationalizations of why it’s appropriate because the person was suspected of XYZ isn’t going to land with them and is largely irrelevant.

But I don’t mind playing devils advocate.

Should the justice system force confessions out of murderers? No, because they are only potential murderers and we have historically been able to get innocent parties to confess. People with vulnerability such as mental health problems are even more likely to give false confessions. The goal of requesting testimony should be honesty not compliance.

This logic applies as well the drug dealer, drug users, and jay walkers. It’s a moral principle disconnected from any specific geography so even if we are not Japanese and have no intention to interact with Japan, we can say they have not lived up to that principle.


I wrote a few of these due to an interest in compilers and hardware.

The easiest syntax to copy if you’re looking for a high level language is Smalltalk.

But most of the time, I wouldn’t even use that. Simple imperative languages that look like BASIC works pretty well in most domains. If you simplify the syntax a little, it’s very easy to understand the compiler and use it for say when you want users to input code into existing systems.


I have written compilers for two families over the years: C and ML. My current preference is Python. I am currently working on a statically typed language that is inspired by Python (minus objects and OOP) that runs on a register VM.

Syntax is a minor issue but something that people are very opinionated about. You could technically build multiple front ends that share the typechecking, CFG validation, optimization, register allocation and byte code emission phases. But it is too much work for what is presently a personal project.


Are they public? Can we study from them? Got later into compilers and I'm trying a little bit of everything

The older ones, no. The current project will be. I am developing in private and occasionally rewriting the jj tree to make each commit self-contained. So it won't contain all the false-starts and bad code, only the cleaned up version.

"ut" (https://github.com/s-i-e-v-e/ut) exists, but it is more of a POC for the syntax more than anything. So lexer+parser+typechecker. Did this during COVID in TypeScript but did not finish.


There are many open source compiler and interpreter projects on github.

also:

https://github.com/BaseMax/AwesomeInterpreter

and probably there is one for compilers too.


I also was curious about this so I did some research.

It looks like age 20 to 34 has the lowest mortality rate. Older or younger than that has higher mortality.

And since 14 to 18 as a cohort are all minors, it’s completely reasonable that parents and society in general discourages this activity.

Taking risks at 35 and 14 are treated differently.


Understandably so.

But what about 18 and 33?

Beyond rare risk of death to the mother, I think the health of the child to be born and the potential for younger siblings is an important consideration since we are talking about reproduction.

In Europe, marriage and pregnancies below 18 were rare and people did use to average 21 before "female education" as well but other cultures differed and differ and I don't know to what extent it is appropriate to have "global" organizations mess with their reproductive lives from a Western perspective whether it has 1820s views or 2020s views.


I picked 14 and 35 for good reason. Both have a higher chance of mortality in pregnancy as a cohort.

Also 14 is relevant for the child marriage article, which is the current context.

18 year olds are not relevant to child marriage.


They are included in the statistics for "high risk" adolescent pregnancy in gp's reference which I take as a condemnation of both adult and minor teenage pregnancies and pregnancies in general.

Argument by absurdity is a well known and to some well regarded rhetorical technique.

It makes you at least agree that there is a line somewhere, and then you can go on to decide where to draw it.


Out of curiosity. What is your first/native language?

In my country, english is hardly anyones first language, but its' mandatory in schools so I've never had the experience with having to find knowledge but its gate-kept behind a translation wall.


My native language is Gujarati. Done my schooling and college in Gujarati too.

Absolutely, I understand what you're saying.

One of the things people miss out, in most of the discussions is that they think "if you were really serious, you would have figured it out". I agree with that in most instances but language and skill acquisition is a complex process as everyone knows.

English being the de-facto reservoir of programming knowledge and applications, it takes substantial amount of time and effort to cross the threshold of understanding and transference.

In any case, I'm an eternal optimist and I believe in action. It was a great experience listening to people's opinion here and I was kind of shocked to find that some of them are so siloed in their chambers, that's interesting nonetheless.


A non-deterministic layer seems like exactly what would need a competent, professional to ensure a good outcome, so it doesn't follow that LLM usage would depress wage more than high-level languages depressed wages by opening up programming to tens of millions of people who could never grok assembly.

> high-level languages depressed wages by opening up programming to tens of millions of people who could never grok assembly.

While I agree with your thesis, I don't think your example actually happened. From my experience teaching CS, the fundamental skill when it comes to programming a computer is algorithmic reasoning, that is, the ability to split a task into subtasks until you reach base tools that you exist in your toolbox. Whether those base tools are MOV or document.getElementById() is largely immaterial, IMO. Obviously it's quicker, and easier, for us to not have to drill all the way down to assembly all the time, but if you have a firm grasp of algorithmic reasoning, you are capable of it.

Algorithmic reasoning is a valuable skill across the economy, one of the most valuable, in fact, right after "risk evaluation" and "having a lot of money", but it's difficult to teach. For some people it seems to fit right into their mental model, and it's simply a "duh". For most, though, it either takes a ton of grinding their head against it, or more often they simply bounce off and decide to do something else. I think that is responsible for the relatively limited supply of developers, which combined with software being wildly profitable because of the whole "copies are free to make" scaling created a shortage, which drove up wages.

They drove up wages so much that approximately everyone who has any aptitude for algorithmic reasoning is now funneled into software development. I think that, more than anything, contributed to the explosive growth of the number of developers. Adults may be hesitant to jump industries, but subsequent generations flooded in.


Home loans are secured by the asset (the home). It's comparable to stock, but it's a less liquid asset.

Any broke person can afford a trillion dollar loan, if they can convince the bank that their house is worth 1.8 trillion dollars. But is that really possible?

Loan companies do due diligence so if GameStop is $A and eBay is worth $A + $B, then so long as $A/$B remains the same, the acquiring company owns two assets worth the full price of the loan.

It doesn't seem to be a scam to me. Am I missing something?


The difference is that when you buy a home the debt is in your name and you are required to pay it off. In a leveraged buy out wouldn't be to person taking out the loan, the debt is owned by the target of the purchase. If it were like a home loan and this deal goes south GameStop would go bankrupt and have to sell it's own assets to cover the losses. But in reality the debt from the deal would be owned by Ebay and if GameStop can't pay the loan back it'd force Ebay into bankruptcy and sell Ebay's assets. It's essentially a riskless move by GameStop and PE in general. Heads GameStop wins tails Ebay loses

From my point of view, they told the kernel security team which is in charge of fixing this. If it’s important for them to tell other people, then it should’ve been written down and further reiterated when they made their report.

The skills to detect code exploits is not the same as the skills to navigate an informal org chart to the satisfaction of an amorphous audience if end users (i.e. us on HN).

That said… as they are a company that supposedly specializes in this field, and is trying to sell a product, I do believe they should do better. Right now, I don’t have much confidence in their product.


Same. I did not know who they were, but now they have been named and shamed. Not every publicity is good.


It is the opposite for me. I did not know who they are and now I have a positive opinion of them.


Can companies decide not to serve you on the basis of a successful lawsuit you had against them?

If not, then it might be better to go the small claims court route.


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

Search: