Sure, I’ve used a variety of other languages (C#, Java, Swift, C, even Scheme etc) and like Go, and even chose it for a solo project.
To me it feels like C with some extra features, kind of like Objective-C. If you need to do some C-like things but can afford the small latency etc overhead introduced by Go, what Go provides (GC, large standard library, green threads, package management, etc) feels like absolute luxury compared to using C. C# is another GC language with the ability to go lower level, but the syntax can also be pretty verbose.
If you’re in the market for an ergo keyboard, I’ve used and liked the Kinesis Freestyle for years now. It’s a fully split keyboard with a staggered layout - I use it in a tented setup, and the ergonomics have been good while it’s similar enough to regular keyboards to not make switching back and forth too difficult.
I’ve tried the mechanical (red switch) version, but actually prefer their membrane version because it’s quieter and I like the tactile feedback better (I haven’t tried the brown/blue switch models though).
> I'm not sure what the difference is with regards to pointers.
In C# most objects are 'class' objects, which are implicitly passed by pointer, although some are 'struct' objects passed by value. In Go rather than making the decision once at the type level, the decision to pass by value or pointer is made explicitly every time an object is used.
> I'm not sure that Go really had anything to figure out or invent
If you look at the discussions for Go (which started as early as 2009 [1]) [2] [3] [4] [5] generics seems as big or a bigger project as the other improvements made to the language over the last decade. My impression is there being a broad spectrum of potential trade-offs across compile speed, execution speed, convenience, etc.
The totality of the prior art here is above my pay grade, but I can quote the Haskell people they roped in [4]:
> We believe we are the first to formalise computation of instance sets and determination of whether they are finite. The bookkeeping required to formalise monomorphisation of instances and methods is not trivial ... While the method for monomorphisation described here is specialised to Go, we expect it to be of wider interest, since similar
issues arise for other languages and compilers such as C++, .Net, MLton, or Rust
I think C# occupies a fairly nice design spot also (and takes advantage of its class/struct system to get fast compiles but also performance when needed). But it's not like the C# design couldn't be improved on. As far as I know you still can't write math code that works across 32 and 64 bit floats. And array covariance is implemented in a way that isn't type-safe and relies on run-time checks and exceptions. [6]
I think C# might be the closest mainstream language, but I’d say explicit pointers, interior pointers, and slices as the default list type might be things that make Go programming a little lower level.
There are also other differences that would prevent using C#’s system as is - Go doesn’t have the reference/value type dichotomy or inheritance. I think they also wanted to be able to abstract across float/doubles etc (unless C# added that recently).
Anyway I like both languages and I’m not trying claim one is better than the other, just trying to explain the design space Go seems to occupy.
I’m not going to defend what random internet commenters may have said, but in my view the core team has been fairly consistent and their design decisions (to me) make sense.
The first thing to understand is that Go occupies a space lower level than Java but higher level than C. It includes things like explicit pointers and more control of memory layout.
Many of the design decisions make no sense without that context. Go can’t simply copy generics from Java or memory sharing from Erlang, since the design decisions made by those languages would introduce too much overhead in a language intended to be lower level. In a lower level language more aspects of how a program executes are specified explicitly, rather than accepting more overhead or guessing what a complex optimizer will do.
On generics, I think the team’s position has mostly been that it’s a big project and there’s been other priorities like rewriting the compiler in Go, improving the GC, etc. And that in the spectrum of trade-offs for generics systems they didn’t want to go all the way to Java or C++.
I feel like a lot of HN commenters compare Go to higher level languages and find it lacking, which may be a fair assessment for certain problems but isn’t really understanding the niche it tries to occupy.
I agree, it seems like an editor based on direct AST manipulation could work pretty well with existing languages (I actually prototyped one a long time ago in university). Some languages like C with text-based preprocessors might cause some headaches but there are others that probably wouldn't be too bad.
There's pretty far you can go with text-based formats since you aren't obligated to display the file exactly as it's stored on disk (and many current IDEs do minor code folding things). For example embedded images can be displayed inline in the source code, but be stored as some loadImage() function on disk. You could even have some comments with base64 binary data if you really needed - at that point binary vs text is mostly a performance issue, but parsing is usually pretty fast so being text-based might still have an advantage because of better interoperability with source control etc.
> The second part looks to be more interesting: I’d like to see some arguments for why a LVT wouldn’t just be passed along to the renters like every other expense is currently.
I think the general idea goes something like: a new apartment can collect $10k/mo rent, and so after construction expenses a developer can pay say $5k/mo for the land. These numbers don't change with a LVT or not.
Without the LVT, the $5k/mo that they can afford translates to say a $500k mortgage, which roughly determines the land price (as multiple developers bid for the same land).
With a LVT, there's say a $2k/mo tax, so they only have $3k/mo to pay the mortgage, which translates to a $300k land price using the same logic.
So by working backwards in this simple thought experiment the LVT is just reducing the value of the land without changing much else about the housing market. Intuitively it also sounds reasonable that taxing land values might reduce land values as a result.
I'd be interested to see the upcoming detailed analysis though.
I agree that people have experiences, but I don't understand why they must be magical or non-existent in the physical world. Why can't the word "experience" simply be referring to the physical processes that happen when our mind/body is in some particular environment?
Certainly physically ingesting a small amount of certain psychedelic chemicals can have profound effects on subjective experience, so it can't be too disconnected from physical processes.
The whole issue of qualia / experiences seems like it is an extension of the dualist/materialist perspectives rather than something that sheds light on it one way or another - dualists will view qualia as something non-material and so something that materialism can't explain, and materialists will view qualia as something material along with consciousness itself.
There are a lot of levels of "thinking" across the animal / insect / even plant kingdoms. The simplest levels of stimulus response (like a venus fly trap closing its mouth) don't seem to require a metaphysical explanation. But insect behavior is more complex and mammal and human behavior even more so.
At which level do the existing rules of the material world start to seem less plausible to you than a second unseen world with different rules, that interacts with this one under specific circumstances (if that's what you mean by dualism)?
As we can presently see with computers and machine learning, pretty complex behavior is possible through systems that operate via known physical processes.
To add to adgjlsfhk1’s answer, if you are writing Android games you are probably using a cross-platform game engine that doesn’t use Java (like Unity) which solves the issue but more importantly also allows you to sell your game on iOS without a re-write.
For memory layout C# actually has an important difference in that it supports value types (so you can have an array of vertices without individually allocating each one, which has a lot of overhead and drastically reduces cache efficiency). They’ve been working on adding support for that to Java for some time but it’s not in yet.
The only advantage I can think of to having a single GC is with using 3rd party packages. If the trade off is always low latency and throughput then libraries know to target that when optimizing, otherwise it’s less clear what to benchmark with.
The corporate world isn't a bad analogy. But corporates are still by and large very profitable, some companies operate as they always have (although that isn't newsworthy, and it isn't a marketing point), and on this specific topic (testing) leetcode type questions are still ubiquitous.
If social trends seriously impaired companies' competitiveness I might expect to see the companies that are more on board underperform. But when I think of recent corporate failures (maybe Google failing to compete with FB on chat / VR / Google plus etc), garden variety mismanagement still seems like it has more impact.
So I also disagree with the policy, but worrying about "transforming the economy to third world status" like the OP seems like it is going overboard. If suboptimal policy choices or social trends destroyed society it would have been destroyed a long time ago many times over (and San Francisco wouldn't be a startup hub).
> So the price of this "equity" movement is going to be (and always was) mass de-industrialization and transforming the economy to third world status
I also disagree with these sort of decisions but this seems a bit hyperbolic. Certain institutions will probably admit fewer students who are able to excel in those fields, and if the change is large enough it will affect the quality of those degree programs (although in probably any admissions process talented students will be better able to game it).
But the likely eventual outcome to that seems like it would be other institutions attracting the most talented students and professors. It's hard for me to imagine every single university getting on board with this, although I could imagine STEM being increasingly concentrated at universities with that focus like Caltech instead of general liberal-arts schools.
It also might be kind of interesting if the brightest students tried to excel more in things that aren't directly competitive (kind of like Thiel fellows), although I don't think that's the purpose behind these sorts of changes.
If the government was restricting the supply of cars / TVs / medicine, etc, causing the prices to be high, you could make a similar argument: why not buy the older car / smaller TV / medicine with more side-effects that you can afford?
That might not be bad advice at an individual level. But it still seems more optimal to allow people to produce more supply, so more people can get what they want and/or spend less of their income to do so.
For housing people generally want access to good jobs, shorter commutes, more space, and lower cost. Those all exist on a spectrum, but more supply would allow, overall, more people to get more of those things.
From a philosophical point of view, there's the question of who has a legitimate interest in what can be built... there's the property owner, the people who own houses in the neighborhood, and the people who work there but commute. There's the people who live in the general metro area, where the overall supply/demand will affect prices.
You could even consider the people left behind by "economic geography" - as fewer people are employed in agriculture etc, there are less jobs in rural areas, and as knowledge work becomes more important more jobs are created in large cities with liquid job markets (which can support greater labor specialization).
I think there's a case to be made that all these levels have some reasonable interest in the outcome and not just the local municipal level. And particularly at the local level there may be some bad incentives - approving more housing may generate local downsides like traffic, while not moving the needle too much on prices which may be determined more by the metro area as a whole.
It's always been incomprehensible to me why they went all the way to production on $500 standalone devices with inside-out tracking but no tracked controllers, then gave up and let Oculus/FB/Meta eat their lunch.
They did the hard part (the inside-out tracking)! And 3D input was obviously a game changer and the future (for VR) to anyone who had tried it out, which included basically everyone who had been to a VR conference at the time (and the tech had been done decently at a consumer level as far back as 2010 with Sony's Move controllers).
Why go all the way to production on a platform that obviously has no future? Why give up right before the basic UX factors are met?
And now they're putting the same person in charge again under 'labs' branding?
It's really hard to be optimistic about this leading to products that go anywhere. Google obviously has tons of tech and talent, but sometimes it feels like they manage to be way less than the sum of their parts due to poor management.
I wonder how coherent the base of either party is values-wise or ideologically. There's certainly some intellectuals that have a clear ideological side, but for the people I talk to offline there often seems to be a kind of sports-team dynamic, even if they don't fit neatly into ideological boxes. For example, I know Republicans that don't generally support their party's economic policies, and Democrats that don't support many of their party's social policies, but neither of those facts seem to interfere with them being solid partisans. Often they end up in a media bubble for their "team" which probably contributes.
I agree that it would affect the US's relative dominance but I don't see why the living standards of Americans would be massively reduced. For things like medical care, housing, education etc those costs are mostly domestic so it seems like the cost of buying foreign currency wouldn't make a huge difference there. The stock market is denominated in USD so at least nominally you'd think it would be OK (although exporters would benefit over importers). Of course it would raise the price of imports, and it looks like imports average around 15% of GDP [1] and exports are around 12% of GDP [2].
So we'd need to manufacture a few % of GDP more in the US for it to balance out. That might make certain things like TVs more expensive, but technology trends have often made those sort of things dramatically less expensive, so overall (and with increased automation) hopefully that wouldn't affect the standard of living too much.
Certainly it might make it harder to attract foreign talent. But hopefully that would mostly be because of increases to the standard of living elsewhere rather than decreases to the US one.
Most of the economy isn't tradeable though, including major sectors like housing, education, health care etc.
If other countries get sick of buying US bonds, the relative value of the currency might depreciate. But as long as it doesn't happen all of a sudden that might not be catastrophic - other countries having stronger currencies might reduce US imports and increase exports (narrowing the trade deficit). Plus increasing automation might mitigate the cost of manufacturing in the US vs overseas.
If I remember correctly, I think Krugman's view is less that there won't be sustained inflation pressure (he's speculated it's transitory, but expressed a lot of uncertainty about it), but rather that the Fed tightening to address that pressure won't necessarily lead to a recession (although of course getting the timing right is tricky).
(I remember him discussing it in detail in this [1] debate with Larry Summers, although it's been a while since I watched it).
That view doesn't seem to contradict the original article, which says prices will increase "unless there is a significant boost in productivity so supply can catch up with demand, or policy makers shift to a tighter stance".
To me it feels like C with some extra features, kind of like Objective-C. If you need to do some C-like things but can afford the small latency etc overhead introduced by Go, what Go provides (GC, large standard library, green threads, package management, etc) feels like absolute luxury compared to using C. C# is another GC language with the ability to go lower level, but the syntax can also be pretty verbose.