@taylorotwell@taylorotwell any plan to offer MariaDB 11.8 since it's technically LTS now and has native vector store support? (as opposed to waiting on PG or MySQL 9.x to become LTS)
@ankurnagpal People were mentioning a week ago that with this great QSBS expansion, they also made AMT apply to it which obviously wasn’t the case before and would negate all the benefits.
Do you know if that was true or ultimately removed? cc @bbalfour
Hi there. I’m your new superpower. 👋
It’s time to stop guessing what people think.
It’s time to trade in your blind spots for true self-awareness.
It’s time to decode reality, once and for all.
Your conversations will never be the same. https://t.co/15H5o520mO
@laravelnews I'm surprised when your newsletter doesn't arrive! Do you all just take some weeks off or didn't get the content scheduled to send in advance? Just curious!
@taylorotwell first, congrats on the round with @Accel, that's amazing.
second, I may be the only VC that's been coding with @laravelphp since 2015 and have loved watching its evolution. it's so delightful to use, @NextGenVP's custom Platform is built with Laravel
third, I know you abhor calls or meetings, but if you or someone on your team ever want to geek out on @laravelphp and world of startups (VC funded or bootstrapped), happy to chat whenever.
🚀 Exciting news! We're thrilled to introduce Narrow AI, our new Automated Prompt Engineering and Optimization platform for AI developers. Say goodbye to "model anxiety" and hello to effortless LLM workflow scaling!
@SandroChess@ankurnagpal Ahh yes, I'm familiar with that article, but just not the 1099 requirement while a LLC as employees of those typically have profits interest or phantom units (LLCs are weird that way :) if you're giving "equity" and I've seen those get converted to shares once a C corp.
@timacdonald87 I had somehow missed the keyBy method which does exactly what I was looking for! No PR needed ;-)
Though I was curious if keyBy is more performant or memory efficient than doing the same thing in a foreach loop?
https://t.co/873uqrZyCz
@timacdonald87 just noticed the 2nd param of the pluck() method (https://t.co/RnBw0t3PCK)
has no one brought up extending the first param to be an array of cols? 1 of the most common use cases I see (& need) is returning DB records indexed by their rec id to refer to in the view
@SandroChess@ankurnagpal I certainly know that investors don't like LLCs though as one myself, an ideal world would be investing in a LLC to let your fund's investors actually benefit from the losses incurred and then have your port co's switch to a C corp if a profit is in site [ignoring QSBS clock :( ]
@SandroChess@ankurnagpal Sorry for the delay in responding. You actually highlighted a point I'm unfamiliar with in terms of the 1099 requirement. You mean while a LLC or once you're a C Corp? Can you point to an article that speaks about this?
@ankurnagpal@SandroChess Alessandro, can you explain that further? I'm very familiar with QSBS and not sure what you're implying or why you say "would not recommend", thx.
@timacdonald87 Essentially you pass less data to the client (i.e. one list of user data) and it's easily referenced by the user ids in the other contexts you're displaying. Thus why it seemed like one could create: pluck(['fname','lname'], id) or pluck(['*'], id) or a new method if needed.
@timacdonald87 Sure. Say you had a dashboard that showed app users in various contexts, e.g. most recent, took some actions, delinquent etc.
instead of joining user info on each of those queries, it's easier to just have the user records by id in an array u can reference in those loops.