Live data from Hacker News

Introducing the LEDE project – A reboot of the OpenWrt community

lede-project.org

11–20 of 82 posts

Re: Introducing the LEDE project – A reboot of the OpenWrt community

#11
post #3

While I'm excited about OpenWrt, why wouldn't the ecosystem move to Raspberry Pi at this point, considering that a Pi and multiple wireless NICs can be purchased for much less than a typical access point?

They are really completely different ecosystems, each with their own use cases, but off the top of my head: 1. Raspberry Pi boards (and rpi-similars) don't typically break out the ethernet interfaces, and require a USB>Ethernet. 2. Raspberry Pi boards (and rpi-similars) don't typically have onboard wifi, this means you will be putting all of your traffic over USB, which as AC rollout happens you don't have enough ban…

What about the Pi 3?

Re: Introducing the LEDE project – A reboot of the OpenWrt community

#12
post #9
post #4

It is a real pity that the lack of developers is compensated by splitting developer focus on two different forks. If the reasons stated are true, let's hope it works out and strengthens embedded Linux, maybe even leading to a reunion like egcs/gcc.

This announcement comes as a surprise to all the other developers, myself included. - mbm (openwrt founder)

This all sounds to me like it was some kind of misunderstanding among the devs. I hope you guys can resolve this and remain together.

While forks can be good, they are not always so.

Re: Introducing the LEDE project – A reboot of the OpenWrt community

#13
post #8

A long time openwrt user here. What puzzles me the most is that, those who are forking openwrt are the the majority group of core developers for openwrt, so I don't know why they are leaving the project they're in control in the first place. It seems a few core developers left behind are also in shock, nobody knows why, and there is no dispute in the community that led to the split either, truly a mystery.

Maybe this is the first step towards launching a commercial offering?

Re: Introducing the LEDE project – A reboot of the OpenWrt community

#14
post #8

A long time openwrt user here. What puzzles me the most is that, those who are forking openwrt are the the majority group of core developers for openwrt, so I don't know why they are leaving the project they're in control in the first place. It seems a few core developers left behind are also in shock, nobody knows why, and there is no dispute in the community that led to the split either, truly a mystery.

It could be that they just didn't want to cause any trouble with attempting to broaden the scope of OpenWRT to more general embedded development rather than a networking focus.

Re: Introducing the LEDE project – A reboot of the OpenWrt community

#15
post #2

More of this type of projects is good, gives consumers/developers more choices.

Not always. If a fork is made because some group wants to move in a different direction code-wise, it's good, because it gives users more choice. However, if the fork is made because of administrative reasons (as it seems to be the case here), then often all it does is muddy the waters and create confusion. We'll see how this one plays out.

Re: Introducing the LEDE project – A reboot of the OpenWrt community

#17
post #13
post #8

A long time openwrt user here. What puzzles me the most is that, those who are forking openwrt are the the majority group of core developers for openwrt, so I don't know why they are leaving the project they're in control in the first place. It seems a few core developers left behind are also in shock, nobody knows why, and there is no dispute in the community that led to the split either, truly a mystery.

Maybe this is the first step towards launching a commercial offering?

this is something to be found out

Re: Introducing the LEDE project – A reboot of the OpenWrt community

#18
post #13
post #8

A long time openwrt user here. What puzzles me the most is that, those who are forking openwrt are the the majority group of core developers for openwrt, so I don't know why they are leaving the project they're in control in the first place. It seems a few core developers left behind are also in shock, nobody knows why, and there is no dispute in the community that led to the split either, truly a mystery.

Maybe this is the first step towards launching a commercial offering?

If so, this blurb from the about page seems interesting:

"LEDE is also an alternation of the phrase to lead, describing an introductory section of a news story that is intended to entice the reader to read the full story."

Re: Introducing the LEDE project – A reboot of the OpenWrt community

#19
post #11

Earlier quoted context omitted.

They are really completely different ecosystems, each with their own use cases, but off the top of my head: 1. Raspberry Pi boards (and rpi-similars) don't typically break out the ethernet interfaces, and require a USB>Ethernet. 2. Raspberry Pi boards (and rpi-similars) don't typically have onboard wifi, this means you will be putting all of your traffic over USB, which as AC rollout happens you don't have enough ban…

What about the Pi 3?

Looks like the rpi3 may have onboard ethernet and wifi, but it's still just one ethernet (100Mbit to boot) and single band wifi.

The point still stands that a $30 router blows away a rpi in terms of network connectivity (which should matter for a router).

Re: Introducing the LEDE project – A reboot of the OpenWrt community

#20
post #3

While I'm excited about OpenWrt, why wouldn't the ecosystem move to Raspberry Pi at this point, considering that a Pi and multiple wireless NICs can be purchased for much less than a typical access point?

In addition to what other folks said, a big part of the user base for OpenWrt and similar use standard hardware from the big consumer electronics firms. I can imagine someone maintaining a port for random experimental platforms (assuming the codebase is amenable that sort of thing; I have no idea), a large part of the point of it for a lot of users would be gone.

But as others said, I can't imagine a Pi having anywhere near the throughput of the commodity AC APs I use at home at this time.

Post reply on HN