Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lahja – A generic event bus implementation written in Python

github.com

Post reply on HN
Print view View original

21–30 of 74 posts

Re: Lahja – A generic event bus implementation written in Python

#21

Post by kgraves »

joshuamorton wrote: post #16
kgraves wrote: post #13

Earlier quoted context omitted.

> Oh please. The EOL on python2 has been massively pre announced. Nope, not when new versions of software comes out with Python 2 still, (can't do anything about those licences bought) small studios cannot afford moving/rewriting tools in P2 to 3, not a priority, rather keep P2.

Then complain to the companies you license software from for continuing to build on a soft-deprecated platform. Don't complain to developers for ignoring a platform whose deprecation was announced over a decade ago. And certainly don't badmouth people who are using the not-deprecated tool as being ok with unstable infra.

> Then complain to the companies you license software from for continuing to build on a soft-deprecated platform.

You think we haven't been doing this? We had a representative from one of these vendors come in to discuss their roadmap, they told us straight up that "We still intend to keep using Python 2".

> Don't complain to developers for ignoring a platform whose deprecation was announced over a decade ago.

Yes, because web dev is the hot tech stuff now, nobody wants to work in a boring sector, so they are not willing to change anything, cycle continues.

> And certainly don't badmouth people who are using the not-deprecated tool as being ok with unstable infra.

I read this sentence twice and I still don't understand what you're trying to say, clarify?

Re: Lahja – A generic event bus implementation written in Python

#22

Post by jsjohnst »

kbumsik wrote: post #15
kgraves wrote: post #10

Earlier quoted context omitted.

Tell that to the industry I work in (Games, Movies & VFX) where most of the tools & 3D software scripting are still in Python 2. Not all of us move fast and break things here, unlike the web dev world.

> Not all of us move fast and break things here, unlike the web dev world. Then how many more years do they need to switch to Python3?

> Then how many more years

Could almost really say “how many decades” at this point.

Re: Lahja – A generic event bus implementation written in Python

#23

Post by jsjohnst »

kgraves wrote: post #13
ggm wrote: post #12

Earlier quoted context omitted.

Oh please. The EOL on python2 has been massively pre announced. Games, Movies and VFX can afford the port costs and have a huge liability looming. There was no "move fast and break things" in this python 3

> Oh please. The EOL on python2 has been massively pre announced. Nope, not when new versions of software comes out with Python 2 still, (can't do anything about those licences bought) small studios cannot afford moving/rewriting tools in P2 to 3, not a priority, rather keep P2.

Can you name some of this software?

Re: Lahja – A generic event bus implementation written in Python

#24

Post by linsomniac »

kitd wrote: post #3

Neat. This feels quite a bit like Vert.x from the Java world, which flows data between components via an event bus. Noob python question: does Python support reactive extensions and chaining? That would fit well on top of this too.

There is RxPY: https://rxpy.readthedocs.io/en/latest/

Re: Lahja – A generic event bus implementation written in Python

#25

Post by th3iedkid »

jsjohnst wrote: post #20
kgraves wrote: post #6

Love to try this out some day, a shame that this isn't in Python 2. EDIT: Thanks HN, try working in an industry where every new project is in Python 2, and have no intention to move on, before saying "moeve to 3", it doesn't help at all.

Does your industry still use Windows XP/Vista, or PHP4, or Ruby 1.8.7, or Apache 1.x, or MySQL 4.1 or RHEL 5? Those are roughly equivalent era.

In an industry where win95 appears to be the norm (if not VAX!) but not complaining when don't see flashy libraries or tools support. It does feel good , when some claim support however.

Re: Lahja – A generic event bus implementation written in Python

#26

Post by joshuamorton »

kgraves wrote: post #21
joshuamorton wrote: post #16

Earlier quoted context omitted.

Then complain to the companies you license software from for continuing to build on a soft-deprecated platform. Don't complain to developers for ignoring a platform whose deprecation was announced over a decade ago. And certainly don't badmouth people who are using the not-deprecated tool as being ok with unstable infra.

> Then complain to the companies you license software from for continuing to build on a soft-deprecated platform. You think we haven't been doing this? We had a representative from one of these vendors come in to discuss their roadmap, they told us straight up that "We still intend to keep using Python 2". > Don't complain to developers for ignoring a platform whose deprecation was announced over a decade ago. Yes, b…

> Yes, because web dev is the hot tech stuff now, nobody wants to work in a boring sector, so they are not willing to change anything, cycle continues.

Change what? You're asking for...what exactly? People to provide support for a deprecated platform? That just encourages those companies you're complaining about to continue to use python2 and further splits the ecosystem. No!

Re: Lahja – A generic event bus implementation written in Python

#27

Post by coldtea »

jsjohnst wrote: post #20
kgraves wrote: post #6

Love to try this out some day, a shame that this isn't in Python 2. EDIT: Thanks HN, try working in an industry where every new project is in Python 2, and have no intention to move on, before saying "moeve to 3", it doesn't help at all.

Does your industry still use Windows XP/Vista, or PHP4, or Ruby 1.8.7, or Apache 1.x, or MySQL 4.1 or RHEL 5? Those are roughly equivalent era.

Python 2.7 is still maintained, and the last version came out in March IIRC, so there's that.

Lots of big players still use Python 2 (Google being the most prominent), and untold smaller players.

Besides, Windows XP and PHP are also in use, as are 50+ year old COBOL systems, so there's that.

Unless you come in and do the port yourself, many systems are not getting ported anytime soon. RedHat and co will continue to release 2.7 patches for the foreseeable future, long after 2020.

Re: Lahja – A generic event bus implementation written in Python

#28

Post by coldtea »

ggm wrote: post #12
kgraves wrote: post #10

Earlier quoted context omitted.

Tell that to the industry I work in (Games, Movies & VFX) where most of the tools & 3D software scripting are still in Python 2. Not all of us move fast and break things here, unlike the web dev world.

Oh please. The EOL on python2 has been massively pre announced. Games, Movies and VFX can afford the port costs and have a huge liability looming. There was no "move fast and break things" in this python 3

>Oh please. The EOL on python2 has been massively pre announced.

Which is neither here, nor there. Pre-announcing doesn't give any reason or motive (or funding) for porting large codebases. Many businesses stuck with 2.x will fund 2.x maintenance if the core devs don't do it, and port on their own schedule not on whatever was "pre announced".

Re: Lahja – A generic event bus implementation written in Python

#29

Post by jnbiche »

kgraves wrote: post #10
solarkraft wrote: post #7

Earlier quoted context omitted.

Please, please don't use Python 2.

Tell that to the industry I work in (Games, Movies & VFX) where most of the tools & 3D software scripting are still in Python 2. Not all of us move fast and break things here, unlike the web dev world.

> Not all of us move fast and break things here, unlike the web dev world.

I had to roll my eyes at that one. Fine if your industry is accepting the high risk of using deprecated releases for new software, but don't try to act like upgrading from deprecated software is "moving fast and breaking things". This deprecation has been announced for 6 years. Python 3 was released over a decade ago.

This ain't a new JavaScript built tool -- this is a carefully planned end-of-life situation for a very old piece of technology.

Post reply on HN