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

> And as far as I can cell, most PhD students don't pay tuition.

Yes, they do. But they receive a full waiver, and that waiver is not taxed.

The proposed tax bill amounts to a several thousand dollar / year increase in the tax load on graduate students, who typically make less than 30k/year.

> So, what stops Harvard from setting a zero tuition for graduate PhD students?

We'll see what clever accounting universities come up with, if any.

But indeed: a $Nk pay-cut could end up having a pretty devastating impact on academia.


Right - so my question is, why not just set a PhD student tuition of zero? They don't make any money off this, so why charge it and always waive it? Why not just get rid of it.

That would remove the option to occasionally charge the tuition, but research PhD programs, especially in STEM at elite universities? Tuition from PhD programs must be close to irrelevant.


As I posted above...they do make money off of it, and quite a bit. They're just not making it off the PhD students.


Two issues:

1. That would mean redefining enrollment. What if a PhD student takes a class that involves instruction time during their research period - as I did, and as some of my students will likely do?

2. The money used to pay the instructors for PhD-level classes, of which there are some, has to come from somewhere. And for many universities, there is $0 that is "irrelevant".


The PI pays the tuition out of a grant, so the university still gets paid for PhD student tuition (just not by the student).

* I'm a professor and I write a lot of proposals to fund graduate students.


This is a bit like saying "disrupt the federal contracting business, so much money for such crap software!"

Standardized tests are a highly political product, and in most states the creation of a standardized test has very little to do with creating an optimal (or even good) assessment.

The idea of using teachers as part of the vetting process for questions is a nice one, but your actual customer sit in state capitols, not classrooms.


I don't think you're entirely wrong, there is political pressure behind standardized testing; however, this is largely because the alternative was no trustable testing. Making teachers' assesments trustable is politically palatable to teachers while also fulfilling the administrative goals that standardized testing has been asked (and largely failed) to resolve.


> How do you verify the verification?

https://mathoverflow.net/a/18436


Apparently the reason is "[tobacco growers] contribute a lot to this country" [1].

You know, as opposed to all of the non-federally-subsidized occupations that contribute literally-anything-other-than-lung-cancer to the country...

I'm assuming the $1.1 million Tobacco spent keeping Richard Burr in office helps him not think too hard about such things [2].

[1] http://thehill.com/blogs/floor-action/senate/301645-senate-r...

[2] http://www.mcclatchydc.com/news/politics-government/article1...


I think there are a lot of reasons to scoff at the "but death saves money" argument. Most of those reasons have to do with the difficulty of accounting for the value of a life fully lived.

E.g., if a highly educated worker dies ten years before retirement, how much productive labor did the society that educated that person lose out on?

What about the non-paid labor that the elderly/retired often take on? "Free" child care for the grand kids, much higher rates of volunteering in churches/schools/etc., and so on.

Suffice it to say that this is not exactly a trivial computation...


I wouldn't say it's trivial, but it does probably save money overall. Highly educated workers are rare overall, and they smoke at much lower rates, so they barely count to the average. The elderly get an income enough to live off plus usually quite a lot of expensive healthcare for many other conditions - and I'm glad they do! But not for financial reasons.


> But does anyone oppose reasonable rules for time-of-day-based noise levels in an apartment or neighborhood?

Even if this were a viable solution, it does nothing for the lost sleep during the months (or in may case, full year) it takes to establish these rules and get them consistently enforced.

Also, it's not a viable solution. There are a couple huge problems.

First, evicting owners is no small thing. In fact, neither is evicting renters. In fact, neither is fining owners/renters for sums of money that would actually cause a change in behavior. These are all very expensive options of last resort that are likely to end in lawyer fees.

Second, with notable exceptions, HOAs/land lords dislike playing mediator/enforcer (and for good reason -- see below). So rules are hard to make and harder to enforce.

Third, there's a real cost imposed on any community that tries to legislate "be a normal neighbor". If you want an enumeration of the potential downsides of this approach, talk to anyone who has had a bad experience with an over-zealous HOA.

You could try to make and enforce a set of rules in a way that solves the problem but doesn't drive normal neighbors insane with pedantic/vindictive rule-violation-reporting. But it turns out that's a rather hard set of rules to come up with/fairly enforce. It's just much easier and, frankly, more effective, to ban airbnb et al.

I'm not opposed to apartment sharing on principle, and in fact my personal political philosophy should bias me toward defending the practice. But my actual experience makes me wary of buildings/neighborhoods that allow airbnb. If airbnb doesn't figure out a solution to this problem, they're going to face increasing resistance.


> Even if this were a viable solution, it does nothing for the lost sleep during the months (or in may case, full year) it takes to establish these rules and get them consistently enforced.

I don't understand that argument. It might make months to establish a ban or effective enforcement of temporary tenants as well. Obviously that sucks, but I'm just trying to think about which rule would be more effective and reasonable.

> First, evicting owners is no small thing. In fact, neither is evicting renters. In fact, neither is fining owners/renters for sums of money that would actually cause a change in behavior. These are all very expensive options of last resort that are likely to end in lawyer fees.

Again, I don't understand. Those are the exact same options we have to disincentivize owners/renters taking in temporary tenants. What alternative enforcement mechanism are you suggesting?

It seems like you're focusing on the difficulties in enforcing my suggestion without recognizing that literally the exact same difficulties exist in enforcing your suggestion.


A more accurate statement might be that the government is paying people to produce cigarettes.


If buying a pack of cigarettes costs less than it would without the subsidies, then you're effectively getting free money every time you smoke.


It's not even close. If the government didn't do any subsidizing or taxing, cigarettes would be much cheaper. The magnitude would vary depending on state or country.


So, let me get this straight. The government pays people to produce them, then charges people to smoke them?


Basically, yes. But it's not quite that clear cut.

Tobacco growers receive farm subsidies [1], which isn't a tobacco-specific subsidy, but also isn't a "whoops didn't mean those farms" accident [2]. Tobacco products are then (heavily) taxed.

Also, it's actually that the federal government pays people to grow tobacco and the state governments tax people to consume tobacco. And the federal subsidies are much lower than the state taxes.

It's still a weird situation, and subsidies probably shouldn't be paid to farms producing tobacco. But the sort of corruption that makes this nonsense possible is totally legal in America, so.

[1] https://farm.ewg.org/top_recips.php?fips=00000&progcode=toba...

[2] http://thehill.com/blogs/floor-action/senate/301645-senate-r...


I think your idea is much better than everything else's, sadly. Yes, some form of tax return bonus would probably be the most effective mechanism.


I'm not sure I agree that "eventually the static types are going to win". The problem is that a lot of program specifications are possible and even economical to write down, but not at all interesting from a research perspective.

I do agree that "eventually statically checked specifications are going to win", but I'm not sold that those specifications will take the form of (something easily recognizable as) a type theory. (However, neither outcome would surprise me).


With apologies to the author, the piece was very well-written but I didn't find any of the arguments or observations in this article comepelling :-(

> This is just a guess, but at the time he wrote Clojure, those type systems most likely were Java-style (Java, C++, C#) and Haskell

SML and OCaml pre-date some of the languages in that list, and certainly pre-date clojure.

The "positional semantics" section -- and that whole class of arguments -- never made any sense to me. All languages have hash maps, so this is about program design rather than language design. Or perhaps, at most, an argument for having nice syntactic sugar for hash maps. In any case, I'm not sure what this has to do with fundamental language design issues. The "can Haskell..." stuff has a similar smell to it. The answer is always "yes, Haskell (and everyone else) have hash maps and HOFs."

At best, it's an argument that those languages should provide a bit of extra syntax around the "everything is a map" programming style. Which, I won't disagree with :)

> In the kinds of systems Rich is talking about, any data could possibly be missing... At the limit, you would need to make everything Maybe

Which is why ML-family languages have both exceptions and algebraic data types.

The discussion of abstraction is just confusing. The author seems to define "abstraction" as "literally any list of information". And I guess it's true that pathologically bad abstractions do exist, but... what point is being made here? I don't get it.

The "screwing around in the type system syndrome" thing actually makes sense, but you can see the same thing in dynamic languages (e.g., with meta-object protocols or macros). There's something more fundamental here, and it's more about human psychology than language design.

I have to agree with keymone, though, that the really interesting thing about clojure is not its design but rather clojure.spec. Sure, you lose a lot of static guarantees, and along with them some of the maintainability/correctness that come along with statically typed languages. But perhaps recovering static checks, and tooling based on static checks, is best done on a library-by-library basis via compositional specification checkers specialized to the particular library. Rather than by a single general-purpose type theory that's rich enough for the "real problems in the messy world" type of programming. And the article kinda starts hinting at this toward the end. But I think keymone really hits the nail on the head when it comes to what you should take away from learning/working in clojure.


> The "can Haskell..." stuff has a similar smell to it. The answer is always "yes, Haskell (and everyone else) have hash maps and HOFs."

+1 !

If necessary you don't need to use and ADT+pattern matching on JSON. You just work with the hashmap directly.


What is the type signature for json hashmap in Haskell and how using it is different from using a dynamically typed language?


The easiest way to use JSON as dynamically typed data in Haskell is with the lens[1] and lens-aeson[2] packages. The type signatures those use are astounding, and not trivial to understand.

But the code that results is very simple while remaining strongly typed.

It ends up being not that different in style from something like hpricot in ruby.

[1] https://hackage.haskell.org/package/lens

[2] https://hackage.haskell.org/package/lens-aeson


A json object has the type signature:

    type Object = HashMap Text Value
which is A JSON "object" (key/value map).

The keys of the hashmap are Text and the leaves are "Value" which contain more JSON

here are different well-formed json values that both resolve to the same type, A.Object (either you get a parse error String for not-well-formed json, or an A.Object)

    >>> A.eitherDecode "{ \"name\": \"Joe\", \"age\": 12 }" :: Either String A.Object

    Right (fromList [("age",Number 12.0),("name",String "Joe")])

    >>> A.eitherDecode "{ \"name\": \"Joe\", \"age\": {\"foo\": \"12\"} }" :: Either String A.Object

    Right (fromList [("age",Object (fromList [("foo",String "12")])),("name",String "Joe")])
Then you can access values in the HashMap by key just like a hashmap in any other language.

Or, as noted by chowells, you can use lens-aeson which can be thought of as a DSL to perform queries in a dynamic fashion:

retrieve value of "foo" in "age"

    >>> s = "{ \"name\": \"Joe\", \"age\": {\"foo\": \"12\"} }" :: String
    >>> s ^? key "age" . key "foo"
    Just (String "12")


> how using it is different from using a dynamically typed language

It's not different for that type. The point of using a statically typed language is you can give static types to other entities in your program!


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

Search: