It is still subsidized, to the tune of 30%. However, that subsidy is mostly because rooftop installs have very high labor costs in the US. Solar farms pay far less per watt.
The actual hardware, especially the panels, have dropped so much in price that if you're capable and willing to do the work yourself you can have a solar install paid off in 2-5 years, depending on how much sun you get and how expensive your local power is. I've seen homebrew setups down south that were paid off in just over a year, but those were guys who live way out in the desert and were getting ripped off by their power company.
One thing you don't see anymore is fancy sun-tracking mounts. Back when panels were expensive they sometimes made sense, but these days it's pretty much always better to just install more panels instead. You can even point them differently, with half facing SE for morning sun and the other half facing SW for evening sun, flattening your production curve and allowing you to use a cheaper and smaller inverter.
One of the ironies in the US is that some of the more conservative states with supposedly renewable energy hostile governments are actually deploying more solar than many liberal states. When people want to oppose a solar install for whatever reason they often turn to environmental laws, requiring impact studies or other such red tape, that are much weaker in conservative states. Texas is a champion of renewable installs despite a government that is openly pro-fossil fuel.
If you could figure out a way to do this economically you could have a real winner. Ground source heat pumps already exist, but they're so expensive to install that they basically never make their cost back vs. air source heat pumps.
Or Australia. For some reason Aussie installers are able to install systems for incredibly affordable prices. I'm always jealous when I see a quote from down under that is like a third of what I paid per watt in the US.
"hypercompetitive and relatively low-regulation installation industry, roofs well suited to work without scaffolding, fairly standardized systems of average size ~8.1kW so not small"
The Obama administration tried, but it was too little too late and they were raked over the coals by Republicans for "choosing winners".
But fundamentally solar cell production was (is?) pretty dirty and US environmental regulations were always going to be a stumbling block. One used to be able to spot Chinese solar factories on satellite maps by looking upstream from deadzones, but apparently that has been enough of an embarrassment that even the CCP has started cracking down.
You would have to burn a cart that contained the webpage and TCP stack, as well as having the ethernet hardware, but there are tricks you can do to reduce the memory requirements. It's not going to be able to handle more than a packet or two at a time, but I've seen TCP stacks squeezed onto really low end hardware. Obviously you won't be able to open much of a TCP window so performance will be lousy, but it's a 1.8Mhz CPU so that was always going to be the case. Just don't have any misconceptions about being able to run TLS on it. Remember that TCP was developed on machines that did not have a lot of memory or even CPU cycles.
An Atari 2600 might be a bridge too far, but a NES should be able to do it.
Fair enough, seems a lot simpler than what I had in mind with expansions and custom software, but also a far cry from OP's "flash" a general purpose OS and more or less get to working
I had the awesome, yet terrible experience to work on an obscure Nintendo feature.
By networking, I am assuming you mean console stack... which I had experience with myself, and yeah... not great. But even more, their web services (more than 10 years ago at this point, hopefully better now) were so, so bad.
The thing that struck me then, and continues to seem true, is how much they just don't really seem to care and that they singularly focus at being good at innovating where it matters: games and differentiated hardware.
Young me thought they were silly for being so "behind the times". Older me respects it more.
> The thing that struck me then, and continues to seem true, is how much they just don't really seem to care and that they singularly focus at being good at innovating where it matters: games and differentiated hardware.
You'd think they'd just admit that and outsource their network-related needs to a company that specializes in that sort of thing.
> The thing that struck me then, and continues to seem true, is how much they just don't really seem to care and that they singularly focus at being good at innovating where it matters: games and differentiated hardware.
Innovating on games with multiplayer and then putting in a wifi chip that gives a ping of like 100ms at best seems like orthogonal goals.
It has been awhile, but from what I remember Nintendo was extremely skimpy with the memory allocated to the TCP stack on the Wii meaning it couldn't open the window up hardly at all and had a tiny bandwidth delay product. This is why updating the system took absolutely forever, even when your local network and the Nintendo servers had ample bandwidth.
Beyond that the servers were also badly implemented and from what I understand they had to call in a third party company to install TCP PEPs[1] in front of the servers to get acceptable performance.
The Wii has ample compute power and memory to max out a Fast Ethernet (100Mbps) port, but due to the design decisions it was barely able to push 1Mbps in real life. This was becoming a problem as system updates were getting larger and the built-in "channel" games were moving beyond NES and SNES ports to actual third party indie titles that sometimes got rather large.
A sidenote is that Wii actually ran a separate operating system (nicknamed IOS by the community) in a dedicated ARM processor (Starlet), that was responsible for performing the majority of device input/output, including disk access, internal and external storage, and notably in this case, networking - the TCP/IP stack was implemented entirely there.
Besides running on a weaker CPU, IOS can access (for exclusive use) some of the main system memory, but it was usually about 12-16MB to not starve the actual games running on the main CPU (https://wiibrew.org/wiki/Memory_map), which can help explain why everything except for the actual games was so slow.
Originally, code running on the main PPC CPU could not access directly most of the IO related hardware at all (only GPU/display output and wired controllers - the bluetooth stack was also on IOS AFAIK, but the Wiimote drivers themselves were userspace), so even the Linux ports had to "proxy" some hardware access through the IOS, but later after reverse-engineering the full boot process, people were able to create a replacement IOS that could enable full access through a special register: https://wiibrew.org/wiki/MINI, enabling full-speed Linux ports, and since that functionality is about a decade old now, I would guess that the NetBSD port also takes advantage of that.
Yeah also in general the WFC code is a bit dated and not very secure.
This actually reminds me of two very interesting bugs which used together basically make it so that you can play WFC games (basically just Mario Kart Wii, nowadays) as simple as changing the DNS settings on your Wii
1. Firstly, as long as you set a particular field in the certificate, it just is completely happy with an invalid cert. (This was fixed by the NWC library by the time it was released In Korea, notably, although this bug was present in DWC for a long while.
(Aside:
I actually suspect that this bug was present in the RVL SDK (used by games and such on the PPC), but also is caused by the same cause as the signing/Trucha bug[1]. While the latter is a IOS specific exploit, it wouldn't surprise me if the same code was used in both this and DWC (the networking library). Given that Mario Kart Wii has an associated IOS version of IOS36[2], but DWC code isn't part of IOS, my hunch is that they used either the same or similar validation logic OR both bugs were squashed a part of some security related cleanup.
I haven't actually gone through the reverse engineering effort to confirm this yet, but given that this doesn't work on the Korean version of MKW, which notably uses a later version of IOS and other libraries, my hunch is that those bugs are one in the same. The fix timing at least seems interesting to me. Anyway side note over.)
2. The networking library also has an RCE caused by a buffer overrun, basically from the first message it has a length that's unchecked and the DWC library blindly memcpys data from the packet. This is kinda why it's important to have some sort of patchset that fixes these bugs (because the operating system and libraries ship with the game and you can't update those except for in memory).
The culmination of this is all you have to do is
1. Change your DNS settings on your unmodified Wii to point to a specified DNS server.
2. Start Mario Kart Wii (probably, although some other games work too), open up WFC
So that the game...
3. Does a DNS lookup for the WFC server which intentionally links to a 3rd party server
4. Passes validation of a bad cert which intentionally sets one of the fields to a null value in order to make the Wii accept it
5. Receives a message that contains an exploit which patches the game in memory to fix the known RCEs and setup URLs to resolve to different domains instead of using the old WFC ones among other things (such as cheat reporting that is all client-side based, etc)
all so you can play Wii games (probably Mario Kart Wii) online 11 years after WFC shut down for good :)
The actual hardware, especially the panels, have dropped so much in price that if you're capable and willing to do the work yourself you can have a solar install paid off in 2-5 years, depending on how much sun you get and how expensive your local power is. I've seen homebrew setups down south that were paid off in just over a year, but those were guys who live way out in the desert and were getting ripped off by their power company.
One thing you don't see anymore is fancy sun-tracking mounts. Back when panels were expensive they sometimes made sense, but these days it's pretty much always better to just install more panels instead. You can even point them differently, with half facing SE for morning sun and the other half facing SW for evening sun, flattening your production curve and allowing you to use a cheaper and smaller inverter.
reply