No, this is more like Monsanto announcing that they have a secret new pesticide that will provide amazing benefits.
Many people criticize it due to Monsanto's track record of causing environmental damage, and due to certain leaks of information that suggest it may be quite bad.
Then you write an article saying that you are all in favor of Monsanto coming out with a new pesticide that strikes a good balance between the interests of the farmer's increased crop yields and the damage to the environment around them.
Do you see what they did there? They not only blew off the concerns of people worried about intellectual property overreach ("balance the interests of consumers and creators of intellectual property" implies that there are two distinct groups of people and that there is some kind of balance between them, which vastly oversimplifies concerns about intellectual property), but by stating their endorsement for this agreement that they haven't seen (even in the abstract, of "we support a good deal that does the right things") they are basically implying that they think the general direction of the deal is positive. Even though they hedge their bets, they are using pretty strongly positive language here.
I would guess a good portion of it, though not all, but that will probably take some time. As a non-profit that provides a widely used web service, they could probably always use more cash, so it's better to get donations now rather than waiting for their insurance to pay out. It's possible they were underinsured on some of this stuff; since they had a lot of custom hardware for scanning books, it may have been hard to price it accurately. It can also be a good fundraising call to arms; people who may have been on the fence or said "well, maybe I'll donate later" now have a reason to donate immediately.
CSS was originally designed only for inline and block layout in a traditional single column of text with left or right floated figures. It has never had any features specifically designed for full page layout, but people have done lots of hacks to use inline, block, margins, padding, and floats to achieve full-page layouts they were never designed for.
There have been improvements in CSS2 and CSS3, like adding table layout so people could at least use the table layout features on div elements rather than abusing tables for layout, and CSS flexbox that work well for standard UI widget layouts.
But the big fixes to layout have been harder to specify and agree upon. They've been in the works for many years, but it's taken a while to figure out how they really should work, and which parts should be fundamental. It looks like it's getting a lot closer; the CSS Grid Module http://dev.w3.org/csswg/css-grid/ is being treated as the fundamental part of the stack on which others will build, it is being worked on by several browser vendors and is in highly active development, and several browsers have implementations in development. It seems to draw elements from IE's experimental CSS grid, as well as the templates of the earlier template layout proposal.
> But the big fixes to layout have been harder to specify and agree upon. They've been in the works for many years, but it's taken a while to figure out how they really should work, and which parts should be fundamental. It looks like it's getting a lot closer; the CSS Grid Module
Although lower-level and not as modular, flexbox can already be used with great success for a number of layout sections (media objects, vertical centering, input inserts) or full layouts ("holy grail", sticky footers and grids): http://philipwalton.github.io/solved-by-flexbox/
Yeah, I think he might have meant ISO-8859-1 or Windows 1252 rather than ASCII; but still, all of those characters would take up two bytes in UTF-8, not 3, unless you used combining diacritics rather than precomposed.
Yes, I meant all of the characters outside of the ASCII range. As in, there are no characters in ISO-8859-1 which take up more than 2 bytes in UTF-8. I guess there are a few in Windows-1252 which take up more than two bytes (like the Euro sign), so it's possible he meant Windows-1252 rather than ASCII.
Are you sure these are startups and not just side projects? Was there any expectation that these would actually grow into larger companies, or were they just part-time mostly self running websites? Not any new business or website is a startup; a startup is specifically one that seeks a scalable business model, that can expand into a much bigger business with more investment, rather than something that is going to be limited by the output of of or a small number of people.
So, I'd be curious about what you are considering a startup such that you have created a few dozen in 3 years.
So, I'm actually looking right now for a microcontroller to run a bunch of real-time I/O that may involve a certain amount of fairly timing dependent bit-banging. I'm planning on building a pinball machine, and so need something that can take input from a couple of buttons, a bunch of switches and some sensors, and drive a bunch of solenoids, LEDs, and the like.
Since I will need to do a bunch of PWM or possibly bit-banged serial protocols to drive all of the LEDs, and I want to have good real-time guarantees on input from the buttons and driving the solenoids, I'm trying to figure out what microcontroller I should use; something like a Propeller, or an FPGA, or maybe one of these, or something else entirely.
Anyone have any experience with these kinds of issues? Will the GA144 be able to do some fairly timing-dependent bit-banging reliably? I notice in the docs that they say the time it takes for each instruction to execute is not fixed. How would you go about doing a timing dependent protocol on these? Is there a high-resolution timer you can poll to ensure that your transitions occur in a timely manner? Or should I bite the bullet and start learning FPGA programming?
Your solenoid response time is likely to be much, much slower than the bit-banging rate of any modern uC. A standard PIC or similar would do fine (assuming it has the I/Os you need).
For solenoids, sure, though some of them (the flipper solenoids) need to be PWMed to vary their strength; you do a full-strength pulse at the beginning to drive the flipper with a good amount of force to hit the ball, but when you hit the end of the stroke, there's a switch that tells you to switch to PWM with a low duty cycle so you avoid overheating the solenoid but can still hold the flipper up to trap the ball. So you need at least the ability to PWM that. Sure, I could probably build a little timer circuit to do that, but it would be convenient if I could just bit-bang a GPIO pin instead of building more hardware.
For driving a few dozen RGB LEDs with PWM to control brightness on each of the three channels, you're very quickly going to reach the limits of what you can do with a standard PIC. Or even if not driving the LEDs directly but using something like these: http://www.adafruit.com/datasheets/WS2812.pdf you need to be able to produce a fairly high precision 800 khz serial signal with no clock.
Between the number of inputs and outputs needed (lots of switches and sensors on the playfield, lots of solenoids to kick out balls and control various toys, lots of LEDs), and the high-speed output needed to drive the LEDs, I'm not sure a standard PIC is going to cut it, though I haven't actually sat down to calculate out the precise number of I/Os and speed that I'll need so I may be wrong. I'm more looking for a ballpark of what I should get a dev board for and start playing around with, I may wind up changing my mind and switching to something else later.
For the LEDs and solenoids I'm guessing the PWM frequency is in the sub 1 kHz range, so you should be able to bit-bang perfectly well with even a low-powered uC. Timing precision for those shouldn't be very strict.
As for the WS2812, that's annoying :) It would be nice if it could use SPI or a UART. I see the NeoPixel library uses bit-banging with interrupts disabled and relies on instruction timing, yuck. But hey, it might work. I've seen single-wire stuff work on Windows CE, for crying out loud. AFAIK you don't need a continuous 800 kHz signal, you can just send it when you want to update.
Yeah, the WS2812 does have a fairly unique interface, but at 45¢ for an RGB LED with a built in constant current driver, it's pretty much the cheapest option per LED. Other options I've seen like the A6281 are $2 for just the driver itself, without the LED.
Since there are probably going to be at least a few dozen LEDs, the per LED cost can add up quickly, so I'm fine with spending a bit more on a more powerful microcontroller or FPGA and learning a new system. And of course, part of the goal is to learn new things and have fun with the project, so some of these new highly parallel microcontrollers like the GA144, Propeller, XMOS, or even an FPGA would be more interesting to work with than a standard PIC, even if they may technically be overkill.
This is the first time I've done hardware hacking in a while; the last time I did it I used a 68008 as my microcontroller. So I'm hoping to find something that will be interesting to learn, not too hard to use, and capable of everything I'm going to throw at it, so I don't have to go through several iterations of buying expensive development boards only to discover that I can't drive my dot matrix display or I can only drive half of the playfield LEDs that I need or that interrupts from the flipper buttons cause my LED color fades to flicker since they screwed up the timing of my signal to the driver or something of the sort.
One of the problems is that since there are so many choices, and I haven't done hardware hacking in a while, I don't have a good sense of what I'll be able to do yet. Maybe I should start small, with an Arduino or a PIC or something of the sort, and move up if I discover that that can't do something that I want.
Coming back into the hardware world after being away for several years, I find the ARM Cortexen pretty damn compelling for the possibility to do the high level programming in something besides C. And a STM32F4 Discovery board is only ~$15.
(And yeah, I feel dirty for blowing up a GreenArrays thread with a suggestion for a more traditional microcontroller, especially not having really studied the GA chip.)
What you're describing seems comfortably doable with a mid-range PIC with a lot of I/Os, but it really depends on how you're looking to program this (and how complex your game logic is going to be). For example, bit banging all of the PWMs can be done from one timer interrupt, but you need to be clever so that it doesn't use too many cycles. Keep in mind at this level, C is considered a high level language.
A FPGA is extreme overkill for this, and keep in mind that you still need some CPU to drive the logic (which could be on the FPGA chip itself, but I don't think this class of FPGA is reasonably priced). A CPLD is still overkill, but at least you don't need to futz with separate configuration memory. And you'll still be doing low-level programming for reconfigurable logic, just in Verilog instead of assembler.
Your level of parallelism isn't actually very high, and I suspect a large single-thread 32-bit microcontroller will do you just fine unless you're looking for an excuse to play with something else.
Your design would be made vastly simpler by using LEDs that have the PWM built in. Then your MCU only needs to write to them when the settings need to change. Adafruit also carries this type. I've tried them and they are very easy to use. The interface is essentially a SPI bus. So, can I assume you're not willing to pay the extra cost for built-in PWM?
You might look into an io expander chip to hook to your pic via I2C or some other protocol. Many of them also have a few PWM outputs. 4, 8, or 16 additional GPIO's are pretty common, and higher pin count expanders are out there, but they get a bit more specialized as the counts go up.
Can you tell me a little about it, and why I should prefer it over a GA144, FPGA, or Propeller? I have a lot of options already, I'm looking to narrow them down, not expand the list to have even more to consider; but if there's a compelling reason I'll take a look.
Yes, that's what inspired me to look into the Propeller, which is an interesting architecture with 8 cores and no interrupts; instead of interrupts, you just dedicate one or more cores to polling for input, while the other cores continue on doing their thing with no interruption.
The GA144 basically looks like an even more extreme version of that idea. Instead of eight small cores, it has 144 really small cores. So now I'm trying to figure out which I want to start playing around with; a Propeller, a GA144, an FPGA, or something else.
Of course it is possible to criticize Ubuntu or Canonical.
What he means is that it's impossible for a prominent developer to criticize their technical decisions without facing a ton of hateful backlash from Ubuntu fans and Mark Shuttleworth himself. Which he knows, from experience, because he did just that, criticized the design of Mir and said that he wouldn't support it, and he got exactly that backlash.
Be respectful
Disagreement is no excuse for poor manners. We work
together to resolve conflict, assume good intentions and
do our best to act in an empathic fashion. We don't allow
frustration to turn into a personal attack. A community
where people feel uncomfortable or threatened is not a
productive one.
Calling people "the Open Source Tea Party", "purely political", "outraged individuals" who have "NIH'd just about every important piece of the stack" is pretty much in pure opposition to the Ubuntu code of conduct; but since Mark does this, other people feel like this kind of behavior is acceptable and pile on the attack.
I thought that was so childish and crass of him. I really dislike the term "Open Source Tea Party". It's just so infuriating on so many levels.
First of all, it's a lazy insult - it's just applying a label (also known as name calling) to put people down without any context. It implies that these people are irrational, inflexible and idealistic, but with a bad connotation. He could have argued that those things are true in a more diplomatic way, and more importantly, by using evidence other than just claiming that mir is "important" or "a huge leap forward for gaming performance...". Instead, he just labels the people who happen to disagree with him as the tea party. Great.
Secondly, I think it's fair to be concerned about what's going on with mir. Maybe he's telling the truth that they just want the best solution... I think everyone, whether you want Wayland or not, would like to move away from X. So maybe mir is the right way to go. However, they failed to make the case for this in a typical open source way. Why not improve Wayland instead of going off and doing your own thing? If the direction of Wayland is awful or wrong, why not point that out? And instead of just claiming that's the case, why not try to use evidence to prove that it's the case? I have been following this closely, but have no idea what the advantages of the two proposed systems is better... but it certainly seems that almost everyone other than Canonical is rooting for and working on Wayland, which isn't really a good sign...
It's very easy to be skeptical because of all the good will they sacrificed by sticking Amazon adds in my god-damned desktop. Honestly, that seems like such a shameless land-grab for clueless users' personal data which really damages their privacy. It wouldn't even have been an issue if it was simply opt in. So, because they made that poor decision, people are skeptical, critical, maybe even a bit irrational. But that shouldn't be surprising. And even if you're being personally attacked yourself, it doesn't make it right to attack other people - many of whom aren't trying to make their contributions a business and are doing their work with pure intentions - unlike Canonical and Mark who clearly have a business angle in all this (which, in and of itself, is totally fine).
Sorry for the rant, guys. I mean, do people really think "open source tea party" is at all fair?
"Sorry for the rant, guys. I mean, do people really think "open source tea party" is at all fair?"
No. If nothing else, it is an insult to the original (Boston) Tea Party. One might remember that those individuals were protesting irrational decisions made by a king who was far isolated from said subjects.
The King had a very rational reason for wanting those taxes. It went quite a bit deeper on the colonial side since they had no say in the matter and expected all the rights of a British citizen.
The implementation of those taxes by using troops and "general warrants" was a problem. Sadly, the formation of thought on that is once again back with us and not imposed by a ruler across the ocean.
As to the modern Tea Party, I guess it depends who you talk to on if they think its an insult.
I think everyone, whether you want Wayland or not, would like to move away from X.
I'm not terribly eager to move away from X. I'll switch if there's something that runs all my programs, and does everything X does but cleaner and better. A POSIXy version of rio from Plan 9 would be a good start.
But Wayland isn't that and I'm not eager to adopt Wayland. Let alone fucking Mir.
Yeah I guess I don't really know what I'm talking about... but having had to open Xorg.conf a couple of times over the past few months I'd be happy to leave X behind.
I am very much rooting for Wayland. It is going to bring features like screen/tmux to graphical programs. Nothing like going to work at home mid day and attaching to the individual programs that you had running on your other machine. This is the reason I currently use terminal programs instead of X ones. Doesn't sound like Mir is providing more over Wayland than just including input, which arguably could be provided outside of the server itself.
Wayland probably isn't going to provide remote display capability, let alone anything like that.
All Wayland really does is hand out framebuffers in local RAM. The Wayland devs consider app display remoting to be a special case used by relatively few users, and outside the scope of the core project.
Yeah, and the nice thing about Wayland barely doing anything is that almost all issues are someone else's problem. The rendering libraries the Wayland developers suggest applications used are totally broken? Not part of Wayland, stop blaming them. XWayland is in a completely unusable state? Not part of Wayland, stop spreading FUD. I remember both of these actually happening.
I do not believe that Wayland would provide this functionality, rather that it would provide separation to enable this functionality. This functionality would be implemented in a compositor for Wayland. There is something similar for X, called Xpra. They list porting to Wayland as one of their "project ideas."
Mir is really important work. When lots of competitors
attack a project on purely political grounds, you have
to wonder what THEIR agenda is. At least we know now who
belongs to the Open Source Tea Party And to put all
the hue and cry into context: Mir is relevant for
approximately 1% of all developers, just those who think
about shell development. Every app developer will
consume Mir through their toolkit. By contrast, those
same outraged individuals have NIH’d just about every
important piece of the stack they can get their hands
on… most notably SystemD, which is hugely invasive and
hardly justified. What closely to see how competitors to
Canonical torture the English language in their efforts
to justify how those toolkits should support Windows but
not Mir. But we’ll get it done, and it will be amazing.
In context, this was written shortly after Martin Gräßlin had said that he would not support Mir in KWin. KWin is the KDE window manager/shell; he is one of those "1% of all developers" for whom the display server really matters. And unlike what Mark claims, KWin does not support Windows (other parts of the Qt and KDE stack do, but not KWin).
So, he sees this as his time essentially being volunteered for him by Mark, to support a display server with an architecture he doesn't agree with, after he's already put the effort in to support the display server that pretty much everyone else in the desktop Linux ecosystem have been targeting. And if you don't agree with Mark, or the technical decisions made leading to Mir, you get branded as "the Open Source Tea Party", "purely political", an "outraged individual" who has "NIH'd just about every piece of the stack."
Maybe I'm being overly pedantic here, but if you're going to call out a project like systemd that is headed in the direction of being the de facto standard in all the other serious Linux distributions, you probably should have looked at the project closely enough to have seen the big deal they make of the correct spelling on their homepage (i.e. systemd vs SystemD). Actually, I'm definitely being overly pedantic here, but his completely dismissive attitude towards systemd makes this KWin post make a bit more sense. Certainly sways me in the direction of agreeing.
No I get that, and I'm not it's biggest fan either, but it's a pretty core component to take the decision lightly. Most of the arguments I see against systemd are very well informed and well reasoned. That's why I categorized his as "dismissive" - and it seems consistent with the accusation that he isn't reasonable, but just doesn't like people disagreeing with him.
seems to imply that the Ubuntu developers will either be the ones to get KDE working on their stack, or go their own way with or without kDE support. It doesn't look like Shuttleworth is insisting through this that Gräßlin devote his time to their project.
Isn't Mir supposed to have XMir as a compatibility layer anyway? Wouldn't this mean that KDE should work on top of it without extra porting work?
There were people announcing that our software will work
just fine on top of their technical stack, others posted
videos showing our software working somewhat on top of
an (IMHO idiotic) hack. It was decided on a mailinglist
I'm not subscribed to that I would walk people through
the KWin code base in a telco for adjusting KWin for
their technical stack. All of that without ever asking
whether we are interested at all. In case of the telco I
was not even asked whether I would want to participate
and whether I have time for that. I experienced this as
a constant pressure and a disrespect to our own
decisions.
It sounds an awful lot like Canonical expecting Gräßlin to spend his time on this project despite the fact that he's not interested in it at all.
Isn't Mir supposed to have XMir as a compatibility layer
anyway? Wouldn't this mean that KDE should work on top of
it without extra porting work?
I believe the XMir compatibility is supposed to be at the application level, not the window manager/compositor level.
KWin is a window manager and compositor, which is fairly specific to the precise graphics stack underneath it.
I wonder how much more successful FPGAs would be if you could actually write your own compilers for them.
As of now, as far as I can tell, none of the major FPGA vendors actually document the actual format of their programming. You have to use a compiler from them to compile a netlist down to the raw bytecode that's actually sent to the FPGA to program it.
This means that there are many potential uses of an FPGA that you just can't do. For instance, you can't write a GLSL shader compiler that compiles down to an FPGA on the fly, or compile OpenCL to an FPGA, or add a language extension that compiles certain highly parallelizable statements in your language down to an FPGA.
It seems that FPGA manufacturers are missing out on an awful lot by not actually opening up their hardware to experimentation by third parties. Anyone know why exactly they act this way?
You can write the tools you describe on top of any existing tool stack -- you'll just have to use the hardware description language as an IL. (Indeed, many tools already do this.)
You could write your own synthesis front-end and place-and-route back-end, but they're not like any compilers you've ever seen before. (A recent Coursera class [1] went into pretty good detail about how synthesis and place and route work.) I think that the unfamiliarity is probably why there are no Open Source toolchains for it.
For Virtex-II platform, Xilinx provided a tool to edit bitfiles, called JBits [2], but it seems to be well and truly dead[3].
Sure, you could use tools that target the HDL as an IL, if you wanted to write that code yourself and then ship it to your customers as a binary blob, as their HDL compilers need to be specifically licensed, and aren't, as far as I know, something designed to be used as a back-end component in shipping software.
But that limits its usefulness for something like, say, writing a GLSL compiler so you can use your FPGA as a GPU, and are then able to run arbitrary GLSL code on it.
I agree that it's definitely a much different than writing a compiler backend for a CPU. You are definitely going to have different abstractions that will apply well to it. But that's fine; that's what I'm interested in, writing a compiler for a very different kind of platform. The problem is, as far as I can tell, they don't document their actual bitstream format, so you must use their licensed tools any time you actually want to compile something new for the FPGA. And that precludes a lot of use cases.
> C-based design entry using the Altera SDK for OpenCL, offering a design environment that is easy to implement on FPGAs
But it seems the release is very early, I was not able to find pricing or even packaging information. It does seem to pack quite a punch, from the performance numbers on the above page ("56 Gbps chip-to-chip/module capability for leading edge interface standards" sounds like ... a lot).
Also, that page has some super-annoying trickery that appends text when you copy and paste, to insert a link back to some Altera page. What idiocy.
So, Altera is able to write an OpenCL compiler for their platform. I am not, because they don't document the low-level bitstream format; you always need to have some licensed Altera compiler in between what you write and the actual hardware.
I was upset when my N1 didn't get the Android 4 release. Apparently, the whole Nexus thing means you are first in line to get updates when they come out (as opposed to carrier phones which frequently get updates several months after they are released, and may never get updates), but that only lasts for about two years.
Although 3rd party developers eventually brought ICS (and Jelly Bean for that matter) to the Nexus One with a lot of hacking, there were good technical reasons why there was never an official release. ICS needed drastically more space on NAND than Gingerbread, as evidence by 3rd party ICS ROMs requiring you to repartition your NAND as well as mount /data on the SD card if you wanted to install more than two or three apps, which then led to greatly reduced I/O performance.
The Nexus One couldn't install ICS or JB because Google and HTC made the stupid decision to give the system only 256 MB of storage--relying instead on the "endless potential" of SD storage to store apps. <facepalm> I can wipe my Nexus One, return to a clean copy of Gingerbread and will still only have about 30 MB of space for apps. What a joke.
Many people criticize it due to Monsanto's track record of causing environmental damage, and due to certain leaks of information that suggest it may be quite bad.
Then you write an article saying that you are all in favor of Monsanto coming out with a new pesticide that strikes a good balance between the interests of the farmer's increased crop yields and the damage to the environment around them.
Do you see what they did there? They not only blew off the concerns of people worried about intellectual property overreach ("balance the interests of consumers and creators of intellectual property" implies that there are two distinct groups of people and that there is some kind of balance between them, which vastly oversimplifies concerns about intellectual property), but by stating their endorsement for this agreement that they haven't seen (even in the abstract, of "we support a good deal that does the right things") they are basically implying that they think the general direction of the deal is positive. Even though they hedge their bets, they are using pretty strongly positive language here.